MCP tools

They all work on the token's site. Arguments and responses have the same shape as the API: everything the API does, the MCP does, and the last column says which route each tool maps to. A test fails if a route shows up without a tool.

Each tool needs a permission. The MCP only shows the tools the token can use; see What the agent can do.

What the agent can do

The same as the person who connected it, based on their role on the site, and never more. The MCP only shows it the tools it can use; a tool it can't see gives Tool not found. In a batch, an operation the role doesn't allow gives key_cannot and nothing is saved.

• It's the role today: if it changes, the agent changes right away, without reconnecting.
• If an owner limited the person to some content types or entries, the agent gets the same limit: it only changes those, and elsewhere it only sees what's published.
• Keys (delivery, preview, management) have no person: their permissions are those of their kind (see API).

What clients confirm

Each tool tells the client what it does to the world, with the standard MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint, title). ChatGPT and Claude use them to decide when to ask you before running a tool: reading goes straight through, publishing or deleting asks first.

Examples

Create and publish, in a conversation:

You: "Create an event Science fair on November 5 at 2:00 PM, and publish it."

The agent calls describe_space to see the fields of event, then create_entry with { "content_type": "event", "fields": { "title": "Science fair", "slug": "science-fair", "startsAt": "2026-11-05T14:00:00-06:00" } }, and publish_entry with the id it got back.

Read with filters:

{ "name": "list_entries", "arguments": { "content_type": "event", "order": "fields.startsAt", "limit": 5 } }

Upload an image:

{ "name": "upload_asset", "arguments": { "filename": "playground.jpg", "data": "<base64>", "title": "Playground", "alt": "Recess in the playground" } }

Or with "url": "https://…" instead of data and filename. Same rules as the API: JPG, PNG, WebP, GIF, SVG or PDF up to 20 MB; MP4 or WebM up to 50 MB.

Migrate lots of things at once:

{ "name": "batch", "arguments": { "operations": [
  { "op": "create_asset", "ref": "playground", "url": "https://…/playground.jpg", "alt": "Recess in the playground" },
  { "op": "create_entry", "ref": "post", "content_type": "post", "fields": { "title": "Hello", "cover": "$playground" } },
  { "op": "publish_entry", "id": "$post" }
] } }

If one operation fails, none are saved, and the error says which one in details.operation.

Translate an entry into a language the site has, then read it before publishing:

{ "name": "add_locale", "arguments": { "code": "en" } }
{ "name": "translate_entry", "arguments": { "id": "12", "to": "en" } }
{ "name": "get_entry", "arguments": { "id": "12", "locale": "en" } }