Payload CMS MCP. Manage site content and globals from your chat.
Payload CMS MCP connects your AI agent directly to your headless content management system. Query collections, update documents, and manage global site settings using natural language commands against the Payload REST API.
Give Claude and any AI agent real-world access
Find single documents or lists of documents across any collection using unique identifiers or complex search filters.
Change the contents of a document, global setting, or user preference by providing a new payload structure.
Permanently delete documents, preferences, or other content types directly through an agent command.
Ask an AI about this
Waiting for input…
What AI agents can do with Payload CMS Alternative: 10 Tools
These tools give your AI agent the ability to perform every core content operation against your Payload CMS backend, from creation to deletion.
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 MCPCreate Document
Generates and saves a brand new entry into any specified content collection.
Delete Document
Removes a specific document from a collection using its unique identifier.
Delete Preference
Deletes a user's stored site preference record.
Find By Id
Retrieves the full data payload for one document when you know its exact ID.
Find Many
Searches and returns a list of multiple documents based on defined criteria or...
Get Global
Fetches the current configuration data for site-wide settings like headers or footers.
Get Preference
Retrieves a specific user's saved preference data by ID.
Update Document
Modifies the text, metadata, or other fields of an existing document in a collection.
Update Global
Changes site-wide settings for global configurations like navigation links or theme...
Update Preference
Updates a specific user's saved preference data in the system.
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.
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 each 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,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Friction of Content Updates
Today, changing a simple headline or updating a product description often means navigating deep into the CMS admin panel. You click to the right collection, find the exact document ID, scroll past old content, manually adjust text in the rich-text editor, and then hit save. If you have dozens of updates across different sections—from the main page banner to related boilerplate copy—you're doing that cycle repeatedly.
With this MCP, your agent handles the complexity. You just tell it: 'Update the site hero banner text to our new slogan.' The agent knows exactly which global field needs modifying and sends the precise command, giving you the change in seconds without ever opening a single admin tab.
Using Payload CMS with find_many
Before this MCP, if product teams needed to audit all articles that mentioned 'AI' but hadn't been reviewed recently, they had to manually build a complex filter query within the collection view. This process was slow and often required technical help just to run the report.
Now, you prompt your agent: 'Find me every post in the blog collection mentioning AI created before June.' The agent executes find_many using all the necessary filters and gives you the exact list of documents needing attention.
What Payload CMS MCP does for your AI
Managing a large website’s content usually means juggling multiple admin dashboards just to make one small change. With this connector, you tell your agent what needs doing, and it handles the backend communication with your CMS. You can ask your agent to find all product listings that haven't been updated in six months, or maybe update the main site footer text across every page.
It treats your content—the documents, the global settings, even user preferences—like a database you talk to. Because this MCP is hosted on Vinkius, you get access to reliable, structured actions for your CMS right from any of your preferred AI clients. You don't need to log into the backend; you just ask, and it executes the required API calls.
019e38d3-d3ad-73fd-bea0-1841b570ad72 How to set up Payload CMS MCP
The bottom line is that you skip the UI entirely; your content changes are managed via secure, conversational instructions.
Subscribe to this MCP and provide the base URL for your Payload CMS instance.
Optional: Supply API keys or authentication slugs if your site requires protected access.
Your AI agent uses these credentials to construct and execute structured API calls based on your natural language request.
Who uses Payload CMS MCP
Content managers who get frustrated having to switch between a CMS and a spreadsheet just to track content status. Developers needing quick ways to verify API responses without running local scripts. Product owners who need to audit site data before launching new features.
Needs to check the publication status of 50 articles and update the boilerplate copy in the global header, all without opening the admin panel.
Wants to query production data directly from their code editor to ensure an endpoint is returning the correct format before writing client-side logic.
Needs to run a bulk content audit, finding every document in a specific collection that lacks required metadata fields for a quarterly review.
Benefits of connecting Payload CMS MCP
Speed up audits by using find_many to query large collections. Instead of building complex queries in the admin panel, you simply ask for 'all draft posts' and get a list immediately.
Never lose track of global settings again. Use get_global and update_global to read or change site-wide elements like footers or header logos without opening the dedicated configuration page.
Automate content drafting by using create_document to quickly populate new entries with structured data, bypassing manual form entry entirely.
Maintain clean data hygiene. You can delete_document and delete_preference directly through your agent when an item is obsolete, ensuring your CMS remains accurate.
Handle complex relationships easily. When searching for content, the system manages relationship depth so you get all necessary related items in one go.
Payload CMS MCP use cases
Auditing outdated site copy
The product team needs to know which articles haven't been touched in 18 months. The agent uses find_many, filtering by last modified date, and returns a list of IDs and titles for review.
Fixing the main footer text
The marketing team realizes the site footer copy is wrong. They ask the agent to update_global on the 'footer' setting, specifying the correct new text instantly.
Testing a content migration
A developer needs to verify that 10 specific product documents exist in staging. Running find_by_id for each ID confirms existence and structure without manual API calls.
Onboarding new users' defaults
The system automatically runs an agent command to update_preference, setting the default language and timezone for a newly registered user account.
Payload CMS MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating it like a simple key-value store
Thinking that simply finding an ID is enough to see all related information, or trying to update complex data without knowing the required JSON structure.
Always use find_many if you need filtered results (like 'all posts in category X'). If you are modifying content, reference the specific documentation for the payload schema to ensure proper updates using update_document.
Relying on UI buttons
Expecting the agent to know which button needs to be clicked or where a setting is located in the CMS backend.
The MCP works by speaking directly to the API. Focus your prompts on data operations: 'Find me X' or 'Change Y to Z'. Use get_global for site-wide settings, not visual descriptions.
Trying to query unrelated services
Asking the agent to check stock levels in an inventory system after fetching content data.
This MCP only controls Payload CMS. If you need external data—like stock or payment info—you must connect a separate MCP for that service.
When to use Payload CMS MCP
Use this if your primary workflow involves managing structured content, site configuration, and user preferences within the Payload CMS environment. It's perfect when your job is defined by 'read data,' 'write data,' or 'change settings.' Don't use it if you need to build a visual component (that requires front-end code) or interact with external systems outside of content modeling (like payment gateways). If your goal is simply viewing the site, this isn't necessary; but if your goal is modifying what powers the site, this MCP gives you direct API control. Remember that using tools like find_by_id and update_document requires precise knowledge of IDs and data structures.
Frequently asked questions about Payload CMS MCP
How does Payload CMS MCP handle complex searches? +
It handles complexity through advanced filtering. You can use tools like find_many to query collections using specific criteria, allowing you to filter by date range, status, or multiple metadata fields.
Can I update global settings with Payload CMS MCP? +
Yes. The get_global and update_global tools allow you to read and modify site-wide configuration data, like the main footer text or navigation links, without touching the visual editor.
What if I need to create multiple documents at once? +
You can ask your agent to run a sequence of create_document calls. It treats each request as a distinct operation and executes them sequentially for you.
Is Payload CMS MCP only for published content? +
No. The tools allow modification across the entire payload, including draft documents in various collections that might not be live on the site yet.
Does this MCP handle user accounts and passwords? +
No. This connector focuses strictly on content modeling (documents, globals) and user preferences stored within the CMS, not user authentication or password management.