Contentful MCP Server

What Contentful MCP Server does

Contentful MCP Server gives MCP-compatible AI assistants access to Contentful Management API operations. It is intended for managing a Contentful space through natural-language requests rather than requiring each operation to be performed manually in the Contentful interface or through custom scripts.

The server covers common content-management areas, including entries, assets, content types, locales, tags, and environments. Supported workflows include creating and updating content, organizing assets, changing content models, publishing or unpublishing content types, and searching entries. It also exposes operations related to Contentful AI actions and space export.

How it works

The server runs as a Node.js process and is commonly started with npx -y @contentful/mcp-server. An MCP client launches the process with environment variables that identify the Contentful space and provide authentication. Requests from the assistant are then translated into Contentful Management API operations.

Each installation targets one space through SPACE_ID. ENVIRONMENT_ID selects the environment used by environment-scoped operations and defaults to master. The Contentful host defaults to api.contentful.com, while EXPORT_BASE_DIR controls the server-side root directory for export_space output.

Setup and configuration

A Contentful account, a Space ID, a Contentful Management API personal access token, Node.js, and npm are required. The minimum configuration is:

{
  "command": "npx",
  "args": ["-y", "@contentful/mcp-server"],
  "env": {
    "CONTENTFUL_MANAGEMENT_ACCESS_TOKEN": "your-CMA-token",
    "SPACE_ID": "your-space-id"
  }
}

Set ENVIRONMENT_ID when the target is not master. CONTENTFUL_HOST, EXPORT_BASE_DIR, and NODE_ENV can be customized when needed. The repository can also be installed from source with npm install followed by npm run build.

The project documents setup paths for Claude Desktop, Cursor, Codex, and VS Code. Claude Desktop can import a DXT configuration from a release, Cursor provides a one-click installation link, and Codex can register the server with codex mcp add.

Tools and capabilities

The documented tool set includes:

• get_initial_context for initializing the connection and returning usage instructions.
• list_content_types and get_content_type for inspecting content models.
• create_content_type, update_content_type, publish_content_type, unpublish_content_type, and delete_content_type for changing content types.
• search_entries for finding and filtering entries.
• Operations for managing entries, assets, locales, tags, environments, and other Contentful resources.
• invoke_ai_action for invoking a Contentful AI action.
• export_space for exporting space data to the configured export directory.

Limitations and notes

The management token determines what the assistant can do in Contentful. The optional PROTECTED_ENVIRONMENTS variable adds an MCP-level safeguard by blocking write and delete calls for listed, case-sensitive environment IDs. Reads remain available, and the guard does not affect direct Contentful SDK calls, the Contentful web app, organization-scoped concepts or concept schemes, or invoke_ai_action.

Unset or empty protection settings leave environments unprotected. The safeguard should therefore complement, rather than replace, Contentful role-based permissions. Export output is confined to the server-controlled base directory configured through EXPORT_BASE_DIR.