Payload CMS

Payload CMS MCP Connector for Claude

A+

Manage headless content via Payload CMS — manipulate documents, patch JSON states, retrieve singletons, and structure database endpoints using AI.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your generative environments explicitly to the Payload CMS Local REST API. Intercept custom database schemas, command explicit content patches natively on document collections, evaluate global singleton items strictly inside Payload limits, and securely query dynamic user states via AI token extraction.

What you can do

  • Document Orchestration — Scan and list explicitly bound arrays parsing defined document collections pulling structured metadata limits locally seamlessly
  • Dynamic Mutation — Instruct the node generating explicit CRUD operations (create_cms_document, patch_cms_document, wipe_cms_document) natively within strict schemas
  • Singleton Validation — Query unique settings files identifying singletons mapping your website configurations logically
  • Advanced User Filters — Trace authenticated arrays filtering specific lists matching identity and identity tracking bounds securely

How it works

  1. Subscribe dynamically connecting this secure instance
  2. Enter your explicitly hosted Payload Base URL and Private API Token parameters
  3. Dominate dynamic REST architectures querying headless CMS logic through Cursor natively

Who is this for?

  • Backend Developers — manipulate complex database items actively running deep schema revisions without explicit physical interfaces
  • Content Engineers — map dynamic content updates directly natively applying JSON payload changes across collections
  • Frontend Teams — isolate singleton configuration outputs validating the state API globally in dynamic response testing
schema-validationjson-apidatabase-managementcontent-orchestrationnode-frameworkrest-api

10 tools expose this connector's capabilities to your AI agent.

create_cms_document

Provision a highly-available JSON Payload writing Rows into Payload

wipe_cms_document

Irreversibly vaporize explicit App nodes dropping live Document rows

get_single_document

Inspect deep internal arrays mitigating specific Row mappings

get_singleton_global

Perform structural extraction of properties driving active Singletons

list_collection_documents

Identify bounded routing spaces inside the Headless Payload Collections

list_payload_users

Identify precise active arrays spanning rented Admin identities

verify_token_identity

Enumerate explicitly attached structured rules defining the Current User

search_collection_where

Retrieve explicit Cloud logging tracing explicit Payload Queries

patch_cms_document

Mutate global Web CRM boundaries substituting database Blocks via ID

update_singleton_global

Dispatch an automated validation check routing Global updates

See how to talk to your AI agent using Payload CMS.

List standard explicit documents isolated under the 'posts' collection.

Called target schema mapping collection 'posts'. Pulled 3 documents natively limit parameters. Docs map details: 1 (ID: a3...), Status: Published. 2 (ID: a4...). Shall I explore JSON content inside ID a3?

Create natively new doc under 'categories', set JSON data `{ "name": "Tech" }`.

Payload confirmed endpoint bounding execution. Created efficiently! New ID assigned logically is '8z9xy2'. Target fields updated explicitly mapping to `{ "name": "Tech" }`. Waiting for next workflow boundaries.

Wipe document logically bounding the ID 'abc12' from the 'media' collection.

Initiated DELETE binding rules. Headless API verified action gracefully. Document ID explicitly 'abc12' has been purged completely from the active 'media' target collection.

Yes. The API agent interacts securely via Payload's standard abstracted REST endpoints. It remains explicitly agnostic of the underlying physical persistence arrays (Mongo/Postgres), resolving logically normalized JSON payloads.

Related Connectors