Developer plugins for Payload CMS 34

Connect AI agents to Payload CMS with the official MCP plugin, or publish an OpenAPI spec of your REST API with Swagger UI or Scalar.

Chat agent that composes and edits Payload pages from your block library

Exposes Payload collections and globals to AI agents through the Model Context Protocol

Lets AI assistants read and edit Payload content over MCP with scoped API keys

Editorial suite that lets teams run a Payload site through MCP tools and AI assistants

Typed block registry and React Server Component renderer for Payload blocks

Runs Payload CMS admin and APIs under vinext, on Node or Cloudflare Workers

Serves a JSON description of a Payload schema and how it maps to database tables

Admin pages that map how collections, globals and blocks link, with an ERD view

Generates one OpenAPI spec for built-in and custom endpoints, with request validation

Serves a JSON description of your Payload site for clients and code generators

Cookie banner, script gating, legal pages and consent records managed in the admin

Adds OAuth 2.1 sign-in with PKCE and dynamic client registration to a Payload MCP server

Syncs Git-hosted Markdown docs into Payload and renders them in a Next.js site

Markdown fields with a CodeMirror editor, styled directives and MCP access for AI agents

Lets AI clients read and edit Payload content over MCP with per-key permissions

Generates an OpenAPI spec from your Payload config and serves it with Scalar or Swagger UI

Generates an OpenAPI spec and docs UI from collections, globals and endpoints

Shared foundation for Throughline that exposes Payload content to MCP tools with audit logging

Serves a design system's component manifest to MCP clients so AI tools compose valid pages

Records content changes and answers who changed what over MCP

About these packages

Developer plugins read collections, globals and endpoints from payload.config. They turn that config into something other software can use. The result can be an MCP server for AI agents, an OpenAPI spec or a JSON schema for code generators.

What these plugins cover

  • The official MCP plugin for exposing collections and globals to AI agents
  • MCP OAuth for OAuth 2.1 sign-in from Claude.ai connectors
  • Community MCP servers with draft-only writes or scoped access
  • OpenAPI spec generators that serve Scalar or Swagger UI
  • Zod API for request validation on custom endpoints
  • Schema Descriptor, Schema Export and Lineage for mapping your schema

Choosing a developer plugin

For AI agents, start with the official MCP plugin. Add MCP OAuth if Claude.ai connectors need to sign in. A community MCP server such as MCPX fits when you want stricter rules, for example writes that stay in drafts. Compare OpenAPI plugins by the docs UI they serve and by whether they cover your custom endpoints. Payload already generates TypeScript types and a GraphQL schema, so check the built-in features before you add a plugin. Programs that run outside Payload are in the tools catalog, under API docs, AI agents and CLI.

Frequently asked questions

How do I connect Claude or another AI agent to Payload CMS?

Add the official MCP plugin to the plugins array. It exposes collections, globals and auth over the Model Context Protocol. MCP OAuth adds an OAuth 2.1 sign-in with PKCE for Claude.ai connectors.

How do I generate an OpenAPI spec for Payload CMS?

Install one of the OpenAPI plugins. They read the collections, globals and endpoints in your config and build a spec from them. Some also serve the spec in Scalar or Swagger UI. Zod API adds request validation with Zod.

Can AI agents edit Payload content safely?

Yes, with limits. Connect the agent through a Payload user or API key that has only the permissions it needs. MCPX limits writes to drafts, and MCP Toolkit scopes which content an AI client can reach.