The connect dialog granting an assistant read content, write content drafts and media, with components and schema off and publishing absent from the list, over the install recipe running npx @bettercms-ai/mcp Connect an assistant Read content Write content drafts Media Components Schema Publishing is not on the list Install recipe npx @bettercms-ai/mcp

Your stack. Your rules. Everyone moves faster.

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.

A vertical line. On the left, everything an MCP grant can hold: read content, write drafts and run skills, each ticked as granted. On the right, the one thing it cannot: a person’s approve-and-publish card with the publish button on it. A single line crosses the divider, labelled request a publish. TWENTY TOOLS, THREE SCOPES A person still presses publish ASSISTANT Read content Write drafts Run skills REQUEST A PUBLISH A PERSON Approve and publish A tool can only ask for it Publish

What the MCP server does

  • Twenty tools, three scopes

    Read, write to drafts and run are granted separately. A tool works only if its own scope was granted.

  • Publishing is not offered

    The ceiling is a publish request, not a publish. An assistant stages the work and then asks.

  • Live content is not edited

    A write against a published entry becomes a proposal. Drafts and staging only, every time.

  • Checks before every call

    The grant, the scope and the workspace switches are read first. The AI budget is checked before a tool runs.

  • Every call is recorded

    Each tool call writes an audit line against its grant. The grant carries its own last-used time.

  • Keys expire and revoke

    The raw value is shown once, then only ever as a mask. One workspace switch suspends every grant at once.

MCP questions.

What teams ask before they connect an assistant to their content.

  • 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.

See the MCP server in your stack

Content OS for modern websites.