AI & MCP
The CMS your coding agent already knows how to use.
Total CMS ships a built-in MCP server. Point Claude Code, Cursor, or ChatGPT at your site and they can read your content, write it back with full validation, and look up this exact install’s documentation.
This page’s documentation is served over MCP by Total CMS. Connect and ask it anything — no install, no signup, no trial.
{
"mcpServers": {
"totalcms": {
"url": "https://totalcms.co/mcp"
}
}
}Four lines into your MCP client’s config. Nothing else to evaluate it.
Version-Matched Docs
Your agent reads your install, not its training data.
An agent working on a Total CMS site gets that install’s documentation — real field names, real Twig signatures, real schema definitions. Not documentation from two years ago, and not an invented API.
Signatures it can't invent
Twig functions and filters are extracted from the running code by reflection, so what the agent reads is what your version actually exposes.
Your schemas, not a guess
An agent asks the site for its collections and fields and gets the real definitions back — including custom schemas that exist nowhere but your install.
Ships enabled
The documentation tools are a bundled extension turned on by default. There is no separate docs server to run and nothing to keep in sync.
Access Control
“Agents can write my content” is a permission decision.
Letting an agent into your site is a decision you make in the same place you make every other permission decision. Access groups govern agents exactly as they govern people — the same system, not a parallel one bolted alongside it.
Three personas
Anonymous public read, API-key admin, and per-user OAuth 2.1 with scopes. A caller is resolved to exactly one of them before a single tool runs.
A real OAuth server
PKCE, refresh tokens, a consent screen, revocation, and an audit log — not an API key wearing an OAuth costume.
Same checks as a person
A Bearer token gets the checks a signed-in user gets. An agent authorised by an editor sees what that editor sees, and nothing further.
Visible, not implied
The Permission Matrix shows exactly what each group can reach, agent reach included, on one screen rather than spread across config files.
Nothing exposed by default
Collections default to admin-only over MCP. A public agent sees what you deliberately published and not one field more.
Writes are validated
Agent writes go through the same schema validation as the admin form. An agent cannot write a field shape your schema forbids.
Why It Works
Your content is a directory of files.
Agents can read and write your content because it is plain JSON on your server. No API rate limits, no vendor in the middle, no export process. The thing an agent is editing is the thing you own, and you can read it with cat.
No rate limits you didn't set
The MCP server is your server. An agent doing a hundred reads is doing a hundred file reads on hardware you control.
Diffable and revertible
Content can live in git. An agent's changes show up as a diff you can read, review, and revert like any other commit.
Nothing to export
There is no export step because there is nothing to migrate out of. The files are already the format.
Boundaries
What it doesn’t do.
Better to find out here than three weeks in.
Public MCP is read-only
Standard gets anonymous read access to content you have published publicly. OAuth, API keys, and agent writes are Pro. A private client site cannot be reached by an agent at all on Standard.
PHP 8.2+, your own server
There is no hosted tier to sign up for. You run it, which is the point, but it does mean you need somewhere to run it.
Flat files have a ceiling
Excellent to a point and honest past it: this is not the right store for millions of records. Filtering large collections is done in memory.
Category
Craft, Statamic and Kirby don’t ship an MCP server.
Not as a plugin, not as a beta. Accurate as of August 2026 — if that changes we will say so here.
Get Started
One command.
composer create-project totalcms/totalcms
Claude Code users
Run tcms skill:install and your agent picks up a Total CMS skill — the conventions, the CLI, and the way schemas are meant to be written.
Standard — $195
Public, read-only MCP over content you publish. One-time, per domain. Everything an agent needs to answer questions about a public site.
Pro — $395
API keys, OAuth 2.1, private content, and agent writes. One-time, per domain. This is the tier if you want an agent working on the site.
Free 45-day trial with every Pro feature · Full pricing · Connect an agent