Twenty tools
Read anything, publish nothing
The server hands an assistant tools for reading content and writing drafts. The highest thing it can do is request a publish, so a person still presses the button.
The BetterCMS MCP server gives an AI assistant twenty tools for reading your content, writing drafts and running skills. The highest thing it can do is request a publish, so a person still presses the button.
Twenty tools
The server hands an assistant tools for reading content and writing drafts. The highest thing it can do is request a publish, so a person still presses the button.
Read, write to drafts and run are granted separately. A tool works only if its own scope was granted.
The ceiling is a publish request, not a publish. An assistant stages the work and then asks.
A write against a published entry becomes a proposal. Drafts and staging only, every time.
The grant, the scope and the workspace switches are read first. The AI budget is checked before a tool runs.
Each tool call writes an audit line against its grant. The grant carries its own last-used time.
The raw value is shown once, then only ever as a mask. One workspace switch suspends every grant at once.
It gets twenty tools for reading content and writing drafts. The highest thing it can do is request a publish.
No. A person decides every publish. That is the boundary the server is built around, not a setting.
It works inside the same model and the same permissions your people do. There is no separate back door into the content.
Any client that speaks MCP. The server is the standard protocol rather than one vendor integration.