Contentful MCP Server

Contentful's official MCP server exposes the Content Management API as tools, so an agent can do the content-operations work that normally means clicking through the web app or writing a one-off migration script.

Coverage

• Content types — list, inspect, create, update, publish, unpublish and delete. This is the part that turns "add a subtitle field to the blog post model across environments" into one request.
• Entries — search and filter, retrieve, create, update, publish and delete, plus get_entry_snapshot for version history when you need to see what a field held before someone changed it.
• Semantic search — semantic_search finds entries by meaning rather than keyword, which matters in a space where the same concept is worded five different ways across a few thousand entries.
• Assets, spaces and environments — the surrounding management surface.

get_initial_context runs first and gives the agent the space's shape and usage instructions before it starts making calls, which is why it behaves sensibly on an unfamiliar space.

Setup

Runs locally over stdio as npx -y @contentful/mcp-server, configured with CONTENTFUL_MANAGEMENT_ACCESS_TOKEN, SPACE_ID and ENVIRONMENT_ID (master unless you are working elsewhere). CONTENTFUL_HOST switches between api.contentful.com and the EU endpoint.

A word of caution

The token this server takes is a Content Management token — it can delete content types and unpublish live entries. Point it at a sandbox environment before pointing it at master, and treat the environment ID as the safety rail it is.

MIT licensed, maintained by Contentful.