home / mcp / contentful mcp server
Provides comprehensive Contentful content management through MCP endpoints for entries, assets, comments, spaces, and content types.
Configuration
View docs{
"mcpServers": {
"ivo-toby-contentful-mcp": {
"command": "npx",
"args": [
"-y",
"@ivotoby/contentful-management-mcp-server",
"--management-token",
"<YOUR_TOKEN>"
],
"env": {
"HTTP_HOST": "localhost",
"HTTP_PORT": "3000",
"CONTENTFUL_HOST": "https://api.contentful.com",
"DISABLE_AI_ACTIONS": "true",
"ENABLE_HTTP_SERVER": "true",
"CONTENTFUL_MANAGEMENT_ACCESS_TOKEN": "<Your CMA token>"
}
}
}
}You can run Contentful’s MCP server locally to manage Contentful content through MCP clients. This server exposes entry, asset, comment, space, environment, and content type management capabilities, enabling large-scale content workflows via a lightweight, transport-agnostic interface.
To use this MCP server you run it as a local process and connect your MCP client to it using either the standard stdio transport or the StreamableHTTP transport. The server supports practical workflows such as creating and updating entries and assets, managing comments with threaded conversations, handling spaces and environments, and performing bulk operations for migrations and batch publishing.
Prerequisites: you need Node.js installed on your machine. The server is run via npm/npx as shown in the usage examples.
# Install and run via stdio transport
npx -y @ivotoby/contentful-management-mcp-server --management-token YOUR_TOKEN
# Alternative: run with a CMA token provided as an environment variable
CONTENTFUL_MANAGEMENT_ACCESS_TOKEN=YOUR_TOKEN npx -y @ivotoby/contentful-management-mcp-serverIf you want to integrate with Claude Desktop, you can add the MCP server to your Claude configuration without cloning the repository. Use the provided example to connect via stdio transport with an authentication token.
{
"mcpServers": {
"contentful": {
"command": "npx",
"args": ["-y", "@ivotoby/contentful-management-mcp-server"],
"env": {
"CONTENTFUL_MANAGEMENT_ACCESS_TOKEN": "<Your CMA token>"
}
}
}
}Placeholders are used for tokens where you must supply your own credentials. Keep your CMA token secure and do not expose it in shared configurations or public tooling. You can also provide a token via a command line argument like --management-token if your setup requires it.
If you encounter authentication or network issues, verify that your CMA token is valid and that you can reach the Contentful API endpoint. Ensure your host and port configurations align with your network policies when using the HTTP transport.
This server exposes a comprehensive set of tools to manage content in Contentful. You can perform entry and asset CRUD operations, manage comments (including threaded discussions), handle space and environment management, work with content types, and perform bulk operations for migrations and batch publishing.
Create, retrieve, update, delete, publish, and unpublish entries with full CRUD capabilities.
Manage comments on entries, including creating, retrieving, updating, deleting, and threading responses.
Upload, retrieve, update, delete, and publish assets with associated metadata.
List, create, update, and manage spaces and environments within Contentful.
List, get, create, update, delete, and publish content type definitions.
Support for multiple locales to adapt content to different regions.
Control publishing workflows for content items.
Execute bulk publish, unpublish, and validate actions across multiple items.