Payload CMS Extended MCP for AI. Query, inspect, and update content data via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Payload CMS Extended connects your AI agent directly to your headless CMS instance. It lets you query collections, inspect document JSON payloads, and perform full CRUD operations—creating, reading, updating, or deleting data—all through natural conversation.
This means you manage content without ever opening the Payload Admin panel.
What AI agents can do with Payload CMS Automation
Create document
Creates a brand new document entry within any specified collection.
Delete document
Permanently deletes an existing document record by its ID.
Get document
Retrieves the full data payload for a single document using its unique ID.
List every collection and global setting defined in your CMS schema so you know exactly what data exists.
Find specific documents across any collection using natural language queries, applying filters, sorting, or pagination parameters.
Retrieve the complete JSON payload for a document ID, showing all associated fields and relationships.
Build or modify entire documents in any collection using structured data input directly from your AI client.
Log into, log out of, and refresh user sessions to ensure the agent has the necessary credentials for sensitive operations.
Ask an AI about this
Waiting for input…
What AI agents can do with Payload CMS Extended MCP Server: 11 Tools for Content Ops
Use these tools to create, read, update, delete documents and global data within your connected Payload CMS instance.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Payload CMS on VinkiusCreate Document
Creates a brand new document entry within any specified collection.
Delete Document
Permanently deletes an existing document record by its ID.
Get Document
Retrieves the full data payload for a single document using its unique ID.
Get Global
Fetches configuration or system settings stored in the CMS global data area.
Get Me
Returns details about the currently authenticated user session.
List Documents
Lists documents from a collection, supporting optional query strings for filtering, sorting, and pagination.
Login User
Authenticates a user account by providing credentials to get an active session token.
Logout User
Ends the current user's session and invalidates authentication tokens.
Refresh Token
Uses a stored refresh token to obtain a new, valid access token for continued API...
Update Document
Modifies the content of an existing document in a collection using its ID and new...
Update Global
Changes system-wide configuration or global settings defined in the CMS.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Payload CMS Extended integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Payload CMS, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Payload CMS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Checking CMS content always means jumping between tabs and panels., Solved with Vinkius AI Gateway
Right now, if you need to find a specific document—say, checking product details or verifying an author bio—you're stuck clicking through the Payload Admin UI. You navigate collections, hit filters, click pagination, copy IDs, and then paste them into your local script. It’s slow, tedious, and easy to miss something.
With this MCP server, you just talk to it. You tell your agent: 'Find all product documents with stock below 10.' The agent runs the query using `list_documents` and returns a clean list of IDs and details instantly. No clicks required.
Payload CMS Extended MCP Server makes content operations simple.
The manual effort of logging into the admin panel, navigating to the right collection, applying filters (date ranges, statuses), and then manually inspecting payloads is gone. Everything happens through a single chat interface.
Your agent acts like it's already logged in and has full read/write access to your data model. It’s not just viewing; it's performing actions—`create_document`, `update_global`, or retrieving user details via `get_me`. That's the difference.
What your AI can actually do with this
You're connecting your AI agent straight to your Payload CMS backend. This isn't just a wrapper; it lets you manage and manipulate all your content data—creating, reading, updating, or deleting records—without ever opening the actual Payload Admin panel. Your agent gets deep access to your entire data model through natural conversation.
Data Awareness: Knowing What You Got
You don't need to switch between your code editor and the CMS console just to verify a field name or check an ID number. The server lets you discover what data exists first. Use list_collections to see every collection defined in your schema, giving you a map of all available content types.
You can also call get_global to fetch system-level configuration and global settings stored outside of any specific collection.
To find documents, use list_documents. This tool lets you search across collections using plain language queries while applying complex filters, specifying sorting parameters, or managing pagination limits. If you need the complete picture for one document, call get_document with a unique ID; this action returns the full JSON payload, revealing every field and relationship associated with that specific entry.
Content Manipulation: Writing to Your CMS
The server gives your agent full write access. You can create brand new documents in any collection using create_document. When content changes, you modify existing records by calling update_document with the target ID and the new data payload. If a record is obsolete, you can permanently delete it using delete_document.
Beyond collections, you manage system-wide settings directly by running update_global, allowing your agent to change configuration values that affect the whole site.
Authentication and Context Control
Because these are sensitive operations, managing user context is key. To start working, you'll first use login_user with credentials; this action provides an active session token needed for all subsequent calls. You can verify who your agent is acting as by running get_me, which returns details about the currently authenticated user session.
When you're done or need to switch users, call logout_user to end the current session and invalidate tokens. If the access token expires during a long workflow, you won't be locked out; you just use refresh_token with your stored refresh token to grab a new, valid access token for continued operation.
019e5d43-6ef9-707a-979b-3e5a58f812d7 
Here's how it actually works
The bottom line is, you treat your CMS like it's just another data source—you talk to it instead of clicking through multiple admin tabs.
Subscribe to this server and provide your Payload CMS Instance URL and API Key.
Your AI client uses the available tools (e.g., list_documents or get_global) to understand your data structure.
You issue a command in plain English (e.g., 'Find all posts by Author X that are published'). The agent executes the necessary API calls and returns structured results.
Who is this actually for?
Anyone who spends time switching context between a code editor and an admin panel needs this. It’s for the developer blocked by manual database checks, the content manager overwhelmed by deep navigation menus, or the DevOps engineer needing to inspect system globals without SSH access.
Runs list_documents and get_document against local or production payloads to verify data structures while writing code.
Uses natural language to find, update, or delete specific entries across multiple collections without navigating the CMS GUI.
Checks system globals using get_global and inspects configuration settings stored in Payload's global data structures.
What Changes When You Connect
Stop context switching. Instead of opening the Payload Admin panel to check a field name or entry status, you simply ask your agent. It handles the query using list_documents and gives you the answer right in the chat window.
Manage credentials without manual steps. Use login_user, get_me, and refresh_token so your AI client can operate with up-to-date, authenticated access for every operation.
Deep data inspection is instant. If you need to know how a document relates to another—like checking associated image metadata—you call get_document and get the full JSON payload immediately.
Built-in content lifecycle control. You don't just read; you write. Use create_document or update_document to push new drafts or modify published records without writing a single line of backend code.
System configuration is exposed. Want to know what the site's main settings are? Call get_global and get the data structure for system-wide variables, which is way faster than digging through config files.
See it in action
Fixing a broken content link.
A Content Manager notices an article links to missing product data. Instead of navigating the CMS manually, they tell their agent: 'Check the Products collection for all documents with status 'draft' that are linked to ID 456.' The agent runs list_documents, identifies the broken entries, and reports them back immediately.
Verifying data during a feature build.
A Developer needs to confirm if their new user profile field (bio) exists in the database. They ask: 'Show me the schema for the Users collection.' The agent runs internal discovery tools and reports back the exact structure, saving hours of guesswork.
Deploying urgent site settings changes.
A DevOps Engineer needs to change the primary contact email displayed across the entire site. They ask: 'Update the global setting for Primary Contact Email.' The agent runs update_global with the new value, confirming the change without needing admin UI access.
Bulk updating outdated records.
A Content Manager finds that all articles published last year need a status update. They ask: 'Find all documents in Posts where published_date is before 2023-01-01 and change their status to 'archived'.'
The agent runs the query (via list_documents) and executes bulk updates using update_document.
The honest tradeoffs
Manual data verification
You open the Payload Admin panel, click 'Posts', apply filters for status='draft' AND date > last month. You have to check pagination pages 1 through 5 just to get a list of IDs.
Just ask your agent: 'List documents in Posts where status is draft and published_date is after last month.' The agent handles the filtering, sorting, and pagination internally using list_documents, giving you a clean list instantly.
Guessing field names
You're coding a new feature and remember that the user profile needs an image URL, but you can't recall if it's called avatar or profileImage. You spend time checking documentation.
Ask your agent: 'What are the fields available in the Users collection?' The agent uses schema awareness to list all valid fields and types for you.
Over-complicating updates
You want to update a post, but instead of telling the AI what changed, you manually construct a massive JSON body with every field name and its old value.
Simply tell your agent: 'Change the title of document ID 65a2b... to 'New Title' and set status to published.' The agent handles generating the precise payload for update_document.
When It Fits, When It Doesn't
Use this server if your workflow involves constant context switching between a code editor and a CMS admin panel. If you frequently need to query structured content, verify field names, or modify records based on natural language instructions, this is for you.
Don't use it if all you need is simple read-only access to external data—a dedicated database client might be better. Also, if your requirements involve complex multi-step business logic that requires human approval at each stage (e.g., 'Draft post > Wait 3 days > Get manager signoff > Publish'), you'll still need a workflow automation tool on top of this. This server handles the data plumbing; it doesn't manage the process itself.
Questions you might have
How does the Payload CMS Extended MCP Server handle authentication? +
It manages standard session flow. You use login_user to get a token, and your agent uses refresh_token if that token expires before you finish your tasks.
Can I list every collection using the list_documents tool? +
You don't use list_documents for discovery. You ask the server to discover collections first, which tells you what data structures are available before running any queries.
Is it safe to run update_document through the AI agent? +
Yes, but your client needs proper API keys and permissions. The tool requires specific instructions on what to change and which document ID you're targeting.
What if I need to check system settings not in a collection? +
You use the get_global tool. This lets your agent read data stored outside of standard collections, like site-wide configuration flags or API keys defined as globals.
When using the list_documents tool, what query syntax do I use to filter by multiple criteria? +
You pass a structured JSON object as the query parameter. This lets you combine filters—for instance, finding documents where 'status' equals 'published' AND 'category' is in ['tech', 'finance']. The agent handles the complex filtering logic for you.
If I run delete_document, how can I confirm I'm deleting the correct record? +
The agent requires explicit confirmation of the document ID and collection name before executing a deletion. It shows you the full payload details first, ensuring you don’t accidentally wipe out critical data.
Does get_document return all associated nested fields and relationships? +
Yes, it fetches the complete JSON payload for that single document. This means you get access to all linked data structures and relationship metadata defined in your Payload CMS schema.
How do I maintain my session if my API token expires while using other tools? +
Use the refresh_token tool when you encounter an authorization error. This automatically validates and replaces the expired credentials, keeping your AI client connected and operational without manual intervention.
How can I see all the available content types in my Payload instance? +
You can use the list_collections tool. Your agent will query your Payload instance and return a list of all registered collections and globals, helping you understand what data is available to interact with.
Is it possible to search for documents with specific criteria, like a slug or status? +
Yes! Use the find_documents tool. You can provide a collection name and filter parameters (e.g., where[slug][equals]=my-post). The agent will return the matching documents including their full metadata.
Can I retrieve the full data of a single document if I have its ID? +
Absolutely. Use the get_document tool by providing the collection name and the unique Document ID. This is perfect for inspecting deep nested relationships or specific field values.
We've already built the connector for Payload CMS Extended. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.