Give your agent the keys to the CMS
Grav 2.0 has a built-in MCP server and a first-party REST API. Point an agent at your site and it can read, write, and publish content the same way you do in the admin, with the same permissions and no sidecar service to run.
How it worksEverything an agent needs, already there
Built-in MCP Server
Point Claude, Cursor, or any MCP client at your site and it can work with your content right away. One click to enable, no sidecar service to babysit.
One API for Everything
The new admin is just a client of the first-party API. Anything it can do, your agent can do, through the exact same REST endpoints.
Real Permissions
An agent authenticates like any other user and inherits that user’s permissions. Scope it to one folder and it stays in that folder.
Markdown In, Markdown Out
Your pages are already plain Markdown and YAML. There is no proprietary rich-text blob for a model to misread or mangle on the way back out.
Every Change is a Diff
Content lives in files, so an agent’s edits land in git like anyone else’s. Review them, revert them, blame them.
AI Pro
A unified provider layer for OpenAI, Claude, Gemini, OpenRouter and custom endpoints, plus an Assistant UI right inside the admin.
AI Translate
One-click translation on any field using DeepL, Google Translate, or the providers you already configured in AI Pro.
Scriptable End to End
The same API drives CI pipelines and cron jobs. Regenerate docs from source, publish on merge, rebuild a section overnight.
No Database in the Way
Copying a site means copying a folder. Nothing to dump, nothing to restore, nothing for an agent to corrupt halfway through.
Why agents get on well with Grav
One API to secure
There is no second API bolted on for the agent. It talks to the same endpoints as the admin, so there is one auth model and one permission model to reason about.
Content a model can read
Markdown and YAML are what language models are best at. Your content goes in and comes back out as text, not as a database row wrapped in editor markup.
Mistakes are cheap
Because the site is files, an agent’s bad afternoon is a git revert. You are never restoring a database to undo a batch of edits.
Nothing extra to run
The MCP server ships with Grav. No queue, no worker, no separate service sitting between your agent and your content.
Point an agent at Grav 2.0
Download, unzip, and you’re live. Turn on the MCP server when you want your agent involved, and it gets the same access you have, no more.