MCP

The MCP server lets AI clients read, and optionally write, structured content in a project. You control the connection from the Studio.

MCP uses its own API keys. GraphQL keys do not work with the MCP server, and MCP keys do not work with GraphQL.

Enable MCP

1. Go to Settings → MCP.
2. Turn on Enabled.
3. Choose a Default Environment, or leave it unset and send X-Environment from the client.
4. Optionally limit Models. Leave the list empty to expose every content model.
5. Turn on Allow Writes only if clients should create, update, or delete entries.
6. Turn on Allow Drafts if read tools should be able to request draft and other non-published statuses.
7. Click Save Settings.

Writes need both settings

Allow Writes is not enough on its own. The client must also use an MCP - Read/Write API key. If either is missing, write tools are not available.

When MCP is turned off, every request returns 403.

Create an MCP API key

Keys are created on the API Keys page, not on the MCP page.

1. Go to Settings → API Keys.
2. Click Create API Key.
3. Choose MCP - Read Only (mcp_) or MCP - Read/Write (mcpw_).
4. Copy the key and store it somewhere safe.

Read-only keys can list and read content. Read/write keys can also create, update, and delete entries, but only when Allow Writes is on. MCP keys cannot change models, components, team members, or billing.

Connect a client

Clients connect to https://mcp.contismo.com. The MCP page shows the connection URL, the required headers, and a Cursor mcp.json snippet.

Send the key as a Bearer token. Send X-Environment with the environment API ID, or omit it to use the default environment configured above.

Authorization: Bearer <your-mcp-api-key>
X-Environment: <environment-api-id>

For tool names, resources, and a full client example, see the MCP server reference.