MCP Servers

A collection of Model Context Protocol servers, templates, tools and more.

M
MCP Tools
by @zubricks
GitHub Repo(1 stars)

MCP Tools Demo

Created 11/17/2025
Updated 28 days ago
README
View Source
Repository documentation and setup instructions

Payload Website Template with MCP Integration

This is the official Payload Website Template, extended with AI-powered content management via the Model Context Protocol (MCP). Use it to power websites, blogs, or portfolios from small to enterprise. This repo includes a fully-working backend, enterprise-grade admin panel, a beautifully designed production-ready website, and intelligent content auditing tools.

This template is right for you if you are working on:

  • A personal or enterprise-grade website, blog, or portfolio
  • A content publishing platform with a fully featured publication workflow
  • AI-assisted content management and optimization
  • Exploring the capabilities of Payload and MCP

Core features:

Quick Start

To spin up this example locally, follow these steps:

Clone

If you have not done so already, you need to have standalone copy of this repo on your machine. If you've already cloned this repo, skip to Development.

Use the create-payload-app CLI to clone this template directly to your machine:

pnpx create-payload-app my-project -t website

Development

  1. First clone the repo if you have not done so already
  2. cd my-project && cp .env.example .env to copy the example environment variables
  3. pnpm install && pnpm dev to install dependencies and start the dev server
  4. open http://localhost:3000 to open the app in your browser

That's it! Changes made in ./src will be reflected in your app. Follow the on-screen instructions to login and create your first admin user. Then check out Production once you're ready to build and serve your app, and Deployment when you're ready to go live.

How it works

The Payload config is tailored specifically to the needs of most websites. It is pre-configured in the following ways:

Collections

See the Collections docs for details on how to extend this functionality.

  • Users (Authentication)

    Users are auth-enabled collections that have access to the admin panel and unpublished content. See Access Control for more details.

    For additional help, see the official Auth Example or the Authentication docs.

  • Posts

    Posts are used to generate blog posts, news articles, or any other type of content that is published over time. All posts are layout builder enabled so you can generate unique layouts for each post using layout-building blocks, see Layout Builder for more details. Posts are also draft-enabled so you can preview them before publishing them to your website, see Draft Preview for more details.

  • Pages

    All pages are layout builder enabled so you can generate unique layouts for each page using layout-building blocks, see Layout Builder for more details. Pages are also draft-enabled so you can preview them before publishing them to your website, see Draft Preview for more details.

  • Media

    This is the uploads enabled collection used by pages, posts, and projects to contain media like images, videos, downloads, and other assets. It features pre-configured sizes, focal point and manual resizing to help you manage your pictures.

  • Categories

    A taxonomy used to group posts together. Categories can be nested inside of one another, for example "News > Technology". See the official Payload Nested Docs Plugin for more details.

Globals

See the Globals docs for details on how to extend this functionality.

  • Header

    The data required by the header on your front-end like nav links.

  • Footer

    Same as above but for the footer of your site.

Access control

Basic access control is setup to limit access to various content based based on publishing status.

  • users: Users can access the admin panel and create or edit content.
  • posts: Everyone can access published posts, but only users can create, update, or delete them.
  • pages: Everyone can access published pages, but only users can create, update, or delete them.

For more details on how to extend this functionality, see the Payload Access Control docs.

Layout Builder

Create unique page layouts for any type of content using a powerful layout builder. This template comes pre-configured with the following layout building blocks:

  • Hero
  • Content
  • Media
  • Call To Action
  • Archive

Each block is fully designed and built into the front-end website that comes with this template. See Website for more details.

Lexical editor

A deep editorial experience that allows complete freedom to focus just on writing content without breaking out of the flow with support for Payload blocks, media, links and other features provided out of the box. See Lexical docs.

Draft Preview

All posts and pages are draft-enabled so you can preview them before publishing them to your website. To do this, these collections use Versions with drafts set to true. This means that when you create a new post, project, or page, it will be saved as a draft and will not be visible on your website until you publish it. This also means that you can preview your draft before publishing it to your website. To do this, we automatically format a custom URL which redirects to your front-end to securely fetch the draft version of your content.

Since the front-end of this template is statically generated, this also means that pages, posts, and projects will need to be regenerated as changes are made to published documents. To do this, we use an afterChange hook to regenerate the front-end when a document has changed and its _status is published.

For more details on how to extend this functionality, see the official Draft Preview Example.

Live preview

In addition to draft previews you can also enable live preview to view your end resulting page as you're editing content with full support for SSR rendering. See Live preview docs for more details.

On-demand Revalidation

We've added hooks to collections and globals so that all of your pages, posts, footer, or header changes will automatically be updated in the frontend via on-demand revalidation supported by Nextjs.

Note: if an image has been changed, for example it's been cropped, you will need to republish the page it's used on in order to be able to revalidate the Nextjs image cache.

SEO

This template comes pre-configured with the official Payload SEO Plugin for complete SEO control from the admin panel. All SEO data is fully integrated into the front-end website that comes with this template. See Website for more details.

Search

This template also pre-configured with the official Payload Search Plugin to showcase how SSR search features can easily be implemented into Next.js with Payload. See Website for more details.

Redirects

If you are migrating an existing site or moving content to a new URL, you can use the redirects collection to create a proper redirect from old URLs to new ones. This will ensure that proper request status codes are returned to search engines and that your users are not left with a broken link. This template comes pre-configured with the official Payload Redirects Plugin for complete redirect control from the admin panel. All redirects are fully integrated into the front-end website that comes with this template. See Website for more details.

Jobs and Scheduled Publish

We have configured Scheduled Publish which uses the jobs queue in order to publish or unpublish your content on a scheduled time. The tasks are run on a cron schedule and can also be run as a separate instance if needed.

Note: When deployed on Vercel, depending on the plan tier, you may be limited to daily cron only.

MCP Plugin & AI Tools

This template includes the official @payloadcms/plugin-mcp which enables AI-powered content management through the Model Context Protocol. The MCP plugin exposes your CMS to AI assistants like Claude Desktop, allowing for intelligent, conversational content operations.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to your tools and data sources. With MCP, you can have natural conversations with AI about your content, and the AI can directly query, analyze, and update your CMS.

Custom AI Tools

This template comes pre-configured with custom AI tools that demonstrate advanced content management capabilities:

🔗 Audit Post Relationships

Tool: auditPostRelationships Purpose: Automatically find and fix posts with missing categories or related post links

What it does:

  • Analyzes all your blog posts to check for proper categorization and internal linking
  • Categorizes posts by severity: Missing Both (🔴), Missing Categories (🟡), Missing Related Posts (🟠), Complete (✅)
  • Calculates an overall relationship health score
  • Can automatically suggest and apply fixes using intelligent keyword matching

How to use:

// Via MCP client (e.g., Claude Desktop)
"Audit my post relationships"

// Via Dashboard Widget
// Navigate to Dashboard → "Post Relationships Health" widget → Click "Run Audit"

// Via Environment Variables (on startup)
RUN_AUDIT_JOB=1 AUDIT_AUTO_FIX=1 pnpm dev

// Via API endpoint
POST /api/audit-posts
{
  "limit": 50,
  "includeUnpublished": false,
  "autoFix": true
}

Implementation:

  • /src/jobs/auditPostRelationships.ts - Core audit logic with smart suggestion algorithms
  • /src/jobs/auditPostRelationshipsJob.ts - Payload Job wrapper
  • /src/app/(payload)/api/audit-posts/route.ts - Custom API endpoint for dashboard widget
  • /src/components/PostRelationshipsAuditDashboard.tsx - Visual dashboard widget

Example output:

# 🔗 Post Relationships Audit Report
Total Posts Audited: 47
Overall Relationship Score: 74/100

Executive Summary:
- ✅ Complete: 35 posts (74%)
- 🟠 Missing Related Posts: 4 posts (9%)
- 🟡 Missing Categories: 5 posts (11%)
- 🔴 Missing Both: 3 posts (6%)

📊 Analyze Content Health

Tool: analyzeContentHealth Purpose: Comprehensive content audit with SEO, freshness, and quality metrics

What it does:

  • Analyzes reading time, content length, sentiment, and freshness
  • Identifies critical issues (missing meta descriptions, poor titles)
  • Detects high-priority problems (outdated content, missing images)
  • Suggests medium-priority improvements (content refresh needed)
  • Provides strategic insights (topic overlap, content gaps, performance patterns)

How to use:

// Via MCP client
"Analyze the health of my blog content"
"Show me posts that need urgent attention"

📝 Additional AI Tools

Draft Release Notes (draftReleaseNotes)

  • Summarizes recent posts with 3 bullet points each
  • Perfect for newsletters or changelogs

Suggest SEO Metadata (suggestSEOMetadata)

  • Analyzes post content and generates SEO-optimized titles and descriptions
  • Follows best practices (50-60 char titles, 150-160 char descriptions)
  • Provides multiple alternatives with character counts

Summarize Post by Slug (summarizePostBySlug)

  • Generates comprehensive summaries of individual posts
  • Extracts key takeaways and content overview

Dashboard Widget

The Post Relationships Audit tool is also available as a visual dashboard widget in the Payload Admin:

  1. Log into Payload Admin
  2. Navigate to Dashboard
  3. Find the "📊 Post Relationships Health" widget
  4. Click "Run Audit" (read-only) or "Run & Auto-Fix" (updates posts)
  5. View results with color-coded breakdown and health score

Using with Claude Desktop

To use these tools with Claude Desktop (requires MCP support):

  1. Configure Claude Desktop to connect to your Payload instance
  2. Start a conversation: "What content tools do I have available?"
  3. Claude will list all available MCP tools including the custom ones
  4. Use natural language: "Audit my posts and fix any relationship issues"

Example conversation:

You: "Audit my post relationships"

Claude: [Analyzes your posts using the audit tool]
"I found 47 posts. 35 are properly connected (74% health score),
but 3 posts are completely isolated with no categories or related posts.
Would you like me to fix them?"

You: "Yes, fix the isolated posts"

Claude: [Applies intelligent suggestions]
"Done! I've assigned relevant categories based on their content
and linked them to related posts on similar topics."

Technical Details

The MCP plugin configuration is in src/payload.config.ts:

import { mcpPlugin } from '@payloadcms/plugin-mcp'

export default buildConfig({
  plugins: [
    mcpPlugin({
      collections: {
        posts: {
          description: 'Company blog posts that can be audited',
          enabled: { find: true, update: true },
        },
      },
      mcp: {
        tools: [
          // Custom AI tools defined here
          // auditPostRelationships, analyzeContentHealth, etc.
        ],
      },
    }),
  ],
})

Key Features:

  • Built on Payload's Jobs system for robust background processing
  • Extensible: add your own custom tools with Zod schema validation
  • Works with any MCP-compatible AI client
  • Can be triggered via API, dashboard, cron, or conversational AI

For more details, see:

Website

This template includes a beautifully designed, production-ready front-end built with the Next.js App Router, served right alongside your Payload app in a instance. This makes it so that you can deploy both your backend and website where you need it.

Core features:

Cache

Although Next.js includes a robust set of caching strategies out of the box, Payload Cloud proxies and caches all files through Cloudflare using the Official Cloud Plugin. This means that Next.js caching is not needed and is disabled by default. If you are hosting your app outside of Payload Cloud, you can easily reenable the Next.js caching mechanisms by removing the no-store directive from all fetch requests in ./src/app/_api and then removing all instances of export const dynamic = 'force-dynamic' from pages files, such as ./src/app/(pages)/[slug]/page.tsx. For more details, see the official Next.js Caching Docs.

Development

To spin up this example locally, follow the Quick Start. Then Seed the database with a few pages, posts, and projects.

Working with Postgres

Postgres and other SQL-based databases follow a strict schema for managing your data. In comparison to our MongoDB adapter, this means that there's a few extra steps to working with Postgres.

Note that often times when making big schema changes you can run the risk of losing data if you're not manually migrating it.

Local development

Ideally we recommend running a local copy of your database so that schema updates are as fast as possible. By default the Postgres adapter has push: true for development environments. This will let you add, modify and remove fields and collections without needing to run any data migrations.

If your database is pointed to production you will want to set push: false otherwise you will risk losing data or having your migrations out of sync.

Migrations

Migrations are essentially SQL code versions that keeps track of your schema. When deploy with Postgres you will need to make sure you create and then run your migrations.

Locally create a migration

pnpm payload migrate:create

This creates the migration files you will need to push alongside with your new configuration.

On the server after building and before running pnpm start you will want to run your migrations

pnpm payload migrate

This command will check for any migrations that have not yet been run and try to run them and it will keep a record of migrations that have been run in the database.

Docker

Alternatively, you can use Docker to spin up this template locally. To do so, follow these steps:

  1. Follow steps 1 and 2 from above, the docker-compose file will automatically use the .env file in your project root
  2. Next run docker-compose up
  3. Follow steps 4 and 5 from above to login and create your first admin user

That's it! The Docker instance will help you get up and running quickly while also standardizing the development environment across your teams.

Seed

To seed the database with a few pages, posts, and projects you can click the 'seed database' link from the admin panel.

The seed script will also create a demo user for demonstration purposes only:

  • Demo Author
    • Email: demo-author@payloadcms.com
    • Password: password

NOTICE: seeding the database is destructive because it drops your current database to populate a fresh one from the seed template. Only run this command if you are starting a new project or can afford to lose your current data.

Production

To run Payload in production, you need to build and start the Admin panel. To do so, follow these steps:

  1. Invoke the next build script by running pnpm build or npm run build in your project root. This creates a .next directory with a production-ready admin bundle.
  2. Finally run pnpm start or npm run start to run Node in production and serve Payload from the .build directory.
  3. When you're ready to go live, see Deployment below for more details.

Deploying to Vercel

This template can also be deployed to Vercel for free. You can get started by choosing the Vercel DB adapter during the setup of the template or by manually installing and configuring it:

pnpm add @payloadcms/db-vercel-postgres

// payload.config.ts
import { vercelPostgresAdapter } from '@payloadcms/db-vercel-postgres'

export default buildConfig({
  // ...
  db: vercelPostgresAdapter({
    pool: {
      connectionString: process.env.POSTGRES_URL || '',
    },
  }),
  // ...

We also support Vercel's blob storage:

pnpm add @payloadcms/storage-vercel-blob

// payload.config.ts
import { vercelBlobStorage } from '@payloadcms/storage-vercel-blob'

export default buildConfig({
  // ...
  plugins: [
    vercelBlobStorage({
      collections: {
        [Media.slug]: true,
      },
      token: process.env.BLOB_READ_WRITE_TOKEN || '',
    }),
  ],
  // ...

There is also a simplified one click deploy to Vercel should you need it.

Self-hosting

Before deploying your app, you need to:

  1. Ensure your app builds and serves in production. See Production for more details.
  2. You can then deploy Payload as you would any other Node.js or Next.js application either directly on a VPS, DigitalOcean's Apps Platform, via Coolify or more. More guides coming soon.

You can also deploy your app manually, check out the deployment documentation for full details.

Questions

If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.

Quick Setup
Installation guide for this server

Install Package (if required)

npx @modelcontextprotocol/server-mcp-tools

Cursor configuration (mcp.json)

{ "mcpServers": { "zubricks-mcp-tools": { "command": "npx", "args": [ "zubricks-mcp-tools" ] } } }