Contentful MCP

Create, edit, publish and delete Contentful entries, assets and models from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Contentful MCP connector does

The Contentful MCP server connects Contentful spaces to Claude and other MCP clients. Its 70 tools read, create, update, publish, unpublish, archive and delete entries, assets, content types, locales, tags, taxonomy and AI Actions. Space administrators decide which tool groups each environment allows, read-only or read and write, through Contentful's MCP app.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Contentful MCP tools (70)

  • append_entry_field
  • archive_asset
  • archive_entry
  • create_ai_action
  • create_concept
  • create_concept_scheme
  • create_content_type
  • create_entry
  • create_environment
  • create_locale
  • create_tag
  • create_upload_session
  • delete_ai_action
  • delete_asset
  • delete_concept
  • delete_concept_scheme
  • delete_content_type
  • delete_content_type_field
  • delete_entry
  • delete_environment
  • delete_locale
  • disable_content_type_field
  • get_ai_action
  • get_ai_action_invocation
  • get_asset
  • get_concept
  • get_concept_scheme
  • get_content_type
  • get_editor_interface
  • get_entry
  • get_entry_snapshot
  • get_initial_context
  • get_locale
  • get_org
  • get_space
  • invoke_ai_action
  • list_ai_actions
  • list_assets
  • list_concept_schemes
  • list_concepts
  • list_content_types
  • list_editor_interfaces
  • list_environments
  • list_locales
  • list_orgs
  • list_spaces
  • list_tags
  • omit_content_type_field
  • publish_ai_action
  • publish_asset
  • publish_content_type
  • publish_entry
  • resolve_entry_references
  • search_entries
  • semantic_search
  • unarchive_asset
  • unarchive_entry
  • unpublish_ai_action
  • unpublish_asset
  • unpublish_content_type
  • unpublish_entry
  • update_ai_action
  • update_asset
  • update_concept
  • update_concept_scheme
  • update_content_type
  • update_editor_interface
  • update_entry
  • update_locale
  • upload_asset

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Large destructive surface. Deletes, unpublishes and delete_environment exist. The mitigation is the per-environment allow-list plus confirmation prompts in your client.
  • App required per environment. The server cannot operate where the Contentful MCP app is not installed.
  • No environment aliases. Use environment IDs.
  • Uploads expire. Upload sessions last one hour and each handle is single-use, per Contentful.
  • No published rate limits. Contentful's MCP page gives none.
  • The local server is different. The open-source @contentful/mcp-server package uses a personal access token with the token owner's full permissions and no per-tool gating. Its SPACE_ID and ENVIRONMENT_ID settings are only defaults.
  • We could not read tool schemas. Tool names come from Anthropic's directory; behaviour from Contentful's documentation. Parameters and annotations are not published here.
  • We called no tool and did not sign in. Our probe was an anonymous initialize and a read of the protected-resource metadata.

Frequently asked questions

Why does a Contentful tool call fail with a not allowed error?

Because that tool's category is not enabled for the space and environment you are working in. Contentful's MCP documentation says administrators choose, per space and environment, which tool categories the MCP app allows and whether each is read-only or read and write. Ask an administrator to update the MCP app configuration, then reconnect the server in your client so the new allow-list applies.

Why do I get Failed to fetch app installation: Forbidden?

Most often because you targeted an environment alias. Contentful's troubleshooting notes say the remote MCP server does not support environment aliases, so a call aimed at an alias rather than an environment can fail this way. Use the underlying environment ID instead, and confirm that the Contentful MCP app is installed in that environment, because the server cannot operate anywhere the app is missing.

Why does sign-in fail or the browser never open?

Usually because the client is holding a stale token. Contentful's guidance is to remove the server from your MCP client and add it again, which restarts the OAuth flow with a fresh token. Each user signs in with their own Contentful identity and selects the spaces and environments for that session, so you may also need to reselect them after reconnecting.

Which endpoint should an EU organization use?

The EU endpoint, not the global one. Contentful documents a separate EU server so that authentication and API calls for EU-provisioned organizations stay on EU infrastructure, and it says the region is fixed by the endpoint with no switch inside a session. If EU calls fail or route oddly, check which URL your client is configured with before anything else.

Sources

Use it in an agent

Put Contentful MCP to work.

Connect Contentful MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.