This MCP server provides integration with Contentful's Content Management API, allowing you to manage content, assets, spaces, environments, and content types through an AI assistant like Claude.
The simplest way to use this MCP server is to add it to your Claude Desktop configuration:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"contentful": {
"command": "npx",
"args": ["-y", "@ivotoby/contentful-management-mcp-server"],
"env": {
"CONTENTFUL_MANAGEMENT_ACCESS_TOKEN": "<Your CMA token>"
}
}
}
}
Alternatively, you can set the token using command arguments:
{
"mcpServers": {
"contentful": {
"command": "npx",
"args": [
"-y",
"@ivotoby/contentful-management-mcp-server",
"--management-token",
"<your token>",
"--host",
"http://api.contentful.com"
]
}
}
}
You can also install the server automatically using Smithery:
npx -y @smithery/cli install @ivotoby/contentful-management-mcp-server --client claude
Configuration can be set through environment variables or command-line arguments:
CONTENTFUL_HOST
/ --host
: Contentful Management API Endpoint (defaults to https://api.contentful.com)CONTENTFUL_MANAGEMENT_ACCESS_TOKEN
/ --management-token
: Your Content Management API tokenYou can scope operations to specific space and environment IDs:
SPACE_ID
/ --space-id
: Contentful space IDENVIRONMENT_ID
/ --environment-id
: Contentful environment IDWhen both are set, tools will only operate within that specific space/environment.
Instead of a management token, you can use Contentful App Identity:
--app-id # App ID providing the token
--private-key # Private key created for your app
--space-id # Space ID where the app is installed
--environment-id # Environment ID where the app is installed
This approach generates temporary app tokens for operations.
List operations return a maximum of 3 items per request to prevent context window overflow. Responses include:
This MCP server grants the AI assistant capabilities to update and delete content, spaces, and content models in your Contentful account. Use with appropriate caution.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.