Contentful MCP Server
Connect AI agents to your Contentful headless CMS — manage entries, content types, and assets via MCP.
Updated
What is Contentful MCP?
The Contentful MCP server is a Model Context Protocol server that gives AI agents structured, tool-based access to a Contentful headless CMS — its entries, content types, assets, spaces, environments, locales, and tags.
Contentful offers this as an official, vendor-hosted remote server at https://mcp.contentful.com/mcp (with an EU endpoint at https://mcp.eu.contentful.com/mcp). Connecting is zero-setup: your MCP client discovers that the server requires OAuth and redirects you to sign in to Contentful in the browser, where you approve the client and choose which spaces and environments are in scope for the session. A per-environment permission layer (the Contentful MCP app) sits on top of your existing Contentful permissions as an additional allow-list.
If you'd rather run it yourself, Contentful also publishes an open-source local server as the npm package @contentful/mcp-server, which authenticates with a Contentful Management API personal access token (CONTENTFUL_MANAGEMENT_ACCESS_TOKEN) instead of OAuth.
Tools the Contentful MCP server exposes
| Tool | What it does |
|---|---|
| get_initial_context | Load setup context the agent needs before making other calls. |
| search_entries | Search content entries by query within a space/environment. |
| get_entry | Fetch a single entry by ID. |
| create_entry | Create a new content entry. |
| update_entry | Update fields on an existing entry. |
| publish_entry | Publish an entry to make it live. |
| list_content_types | List the content types (models) in an environment. |
| create_content_type | Create a new content type / content model. |
| upload_asset | Upload a media asset to a space. |
| list_environments | List environments within a space. |
Connect the Contentful MCP server
Claude Code (remote, OAuth)
- 1
Add the remote server
Run: claude mcp add --transport http contentful https://mcp.contentful.com/mcp (use https://mcp.eu.contentful.com/mcp for the EU region).
- 2
Authenticate via OAuth
On first use, the client detects the server requires OAuth and opens Contentful in your browser. Sign in and approve the spaces/environments in scope.
- 3
Verify
Run /mcp in Claude Code to confirm the contentful server is connected, then ask the agent to list your content types.
Cursor (remote, OAuth)
- 1
Edit your MCP config
Open ~/.cursor/mcp.json (or .cursor/mcp.json in your project).
- 2
Add the Contentful server
Add: { "mcpServers": { "contentful": { "url": "https://mcp.contentful.com/mcp" } } } — swap in https://mcp.eu.contentful.com/mcp for the EU region.
- 3
Sign in
Reload Cursor; it discovers the OAuth requirement and redirects you to Contentful to authorize and pick the spaces/environments in scope.
Sample use cases
Draft and publish blog posts or landing pages directly from an agent
Content moves from idea to published entry without leaving the agent workflow.
Migrate content between environments (e.g. staging to production)
The agent reads entries from one environment and recreates them in another, handling references and assets.
Bulk update entries matching a specific field pattern
The agent searches for entries by content type or field value and patches them in one pass.
Audit content for missing fields, broken references, or stale entries
The agent lists entries with empty required fields or references to deleted content and flags them for review.
Create new content types to extend the CMS schema
The agent defines a content model programmatically, reducing manual clicks in the Contentful web app.
Upload and attach media assets to entries programmatically
The agent uploads images or documents and links them to the correct entry fields.
Schedule content reviews by querying entries not updated in 90+ days
A scheduled agent surfaces stale content so editorial teams can refresh or archive it.
List and compare content types across environments
The agent pulls content models from staging and production and highlights differences before a deploy.
Security & permissions
The remote server uses an OAuth 2.1 flow: you sign in to Contentful through your MCP client and approve which spaces and environments are in scope for the session. The MCP app does not replace your underlying Contentful permissions — it sits on top of them as an additional per-environment allow-list, and admins can decide which tool categories are available in each environment. The self-hosted local server instead uses a Contentful Management API personal access token (CONTENTFUL_MANAGEMENT_ACCESS_TOKEN); scope it to only the spaces and environments the agent needs.
Using Contentful MCP with Gamut
In Gamut, the Contentful MCP server becomes a tool your agents can call inside automated, event- or schedule-triggered workflows — for example, a scheduled run that drafts and publishes new entries, updates content-type fields, or audits and tags assets across an environment. Gamut manages the connection and OAuth session, so an agent can search entries, create or update content, and publish changes as steps in a larger pipeline without a human wiring up credentials each time. Scope stays bounded by the spaces, environments, and permissions you grant on connect.
Frequently asked questions
What is the Contentful MCP server?
It's an official Model Context Protocol server from Contentful that lets AI agents and clients read and manage a Contentful headless CMS — entries, content types, assets, spaces, environments, locales, and tags — through standardized tool calls.
Is the Contentful MCP server free?
There is no separately documented fee for the MCP server itself; access follows your existing Contentful plan and account permissions. The local server (@contentful/mcp-server) is open source, and the remote hosted server is offered in beta.
How do I connect the Contentful MCP server to Claude or Cursor?
Point your client at the remote server URL https://mcp.contentful.com/mcp (or the EU endpoint). For Claude Code, run claude mcp add --transport http contentful https://mcp.contentful.com/mcp; for Cursor, add it under mcpServers in ~/.cursor/mcp.json. The client opens an OAuth flow to sign in.
Is the Contentful MCP server hosted or self-hosted?
Both. Contentful hosts a remote server at https://mcp.contentful.com/mcp (OAuth, zero setup), and also publishes an open-source local server as the npm package @contentful/mcp-server that you self-host using a Contentful Management API token.
Can the agent publish entries to production?
Yes. The publish_entry tool makes an entry live immediately. Scope safety by restricting the API token's role to specific spaces or environments, or use the agent only in staging.
Does it work with Contentful's localization features?
Yes. Contentful entries store per-locale field values, and the agent can read and write localized content through the same entry tools. List environments shows which locales are configured.
Can I restrict the agent to specific spaces or environments?
Yes. Generate a Contentful Management API token scoped to specific spaces and environments. The agent can only access what the token permits, keeping production content safe during development.