A headless CMS MCP server for AI agents.
Coming soonConnect Cursor, Claude Desktop or any MCP client so agents can read and update your sites — with the same permissions as the member who connects. Until it ships, use Copy prompt for AI to teach assistants your HTTP API.
What agents can do
Pages, content and leads — as tools.
The MCP server exposes the same jobs your team does in admin, as named tools an agent can call. Writes go to Development; Production only changes through a Release, just like a human editor.
Pages and sections
List pages, add sections, define fields and fill them in — only what the member's level allows, and only what you ask to make dynamic.list_pagesupdate_sectionItems on list pages
On a page with many items, list, read and update entries — packages, properties, courses — by the site's own schema.list_itemsForms
Read form definitions so an agent can explain fields or wire a frontend — submissions still hit the public Form API.get_formLeads
List and update leads the member can already see: status, owner, follow-up — never across another website.list_leadsupdate_lead
Same access as your team
The agent only gets what that member already has.
No god-mode MCP key. You connect as a website member; tools fail closed when the module level is missing. Clients stay Editors on Pages — never on API keys.See how team access works
Bound to a member
The connection is that person's session or token. Revoke their access and the agent loses the tools.Website memberPer-module levels
Viewer, Editor, Developer, Admin — the same bundles admin already uses. No inventing a separate MCP permission.ViewerEditorOne website at a time
Tools are scoped to the active website. An agent never lists another client's pages from the same connection.Tenant isolatedSecrets stay out
API keys, storage secrets and AI provider keys stay in Developer settings. Content editors' agents never see them.mwc_live_… hidden
How you'll connect
One MCP server. Your usual AI clients.
Coming soonAdd mywebcms as an MCP server in Cursor, Claude Desktop or any client that speaks the protocol. Sign in as a website member; tools inherit that person’s access. The shape below is the intended config — the endpoint isn’t live yet.
Intended · Cursor mcp.json
{
"mcpServers": {
"mywebcms": {
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer …"
}
}
}
}Exact auth (member session vs website token) lands with the ship. Until then, teach assistants the HTTP API with Copy prompt for AI.
Any MCP client
Cursor, Claude Desktop, Claude Code and other MCP hosts — same tools, same permissions.CursorClaudeMCPPer website
Point the client at one website. Switch sites by reconnecting as a member of that site — no cross-tenant tools.One site · one connectionSame RBAC
Editors update content in Development. Developers can change structure. Agents can open a Release, but only people approve and merge it.Module levelsWorks next to HTTP
MCP doesn't replace the Content Delivery or Form APIs. Frontends still read JSON over HTTP; agents get tools for admin work./v1 + MCP
Two ways to work with AI
Agents that call tools. Assistants that write code.
MCP is for managing content through tools. Copy prompt for AI is for generating the site that reads that content. Use both when both ship — today, start with the prompt.See AI on both sides of the API
- Coming soon
MCP server
Agents call named tools — list pages, update a section, work leads — under the connecting member's access. Best when the assistant should act inside mywebcms, not just generate code.
- Structured tool calls
- Live reads and writes in Development
- Same permissions as that member
- Available now
Copy prompt for AI
Admin builds a prompt that teaches Cursor, Claude Code or any coding assistant your page's Content and Form API endpoints. They write the frontend; mywebcms stays the source of content.
- Plain HTTP + JSON
- Any stack the assistant can write
- No MCP client required
FAQ
Questions about CMS MCP.
Availability, permissions, Production, and how MCP sits next to prompts and AI import.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.