Mcp Server
Manage Kontent.ai content models, entries, taxonomies, and workflows from your coding agent without living in the web UI.
Overview
io.github.kontent-ai/mcp-server is a MCP server for the Build phase that lets agents manage Kontent.ai content, types, taxonomies, and workflows via the Management API.
What is this MCP server?
- Natural-language control of Kontent.ai content, types, taxonomies, and workflows
- npm @kontent-ai/mcp-server v0.33.1 with stdio and streamable-http (localhost:3001) modes
- Requires KONTENT_API_KEY and KONTENT_ENVIRONMENT_ID
- Positional args stdio vs shttp select transport when launching the package
- Package version 0.33.1
- Two transports: stdio and streamable-http on localhost:3001
- Two required env vars: KONTENT_API_KEY and KONTENT_ENVIRONMENT_ID
Community signal: 9 GitHub stars.
What problem does it solve?
Constant context-switching between your repo and the Kontent.ai UI slows every schema tweak and content fix during a solo build sprint.
Who is it for?
Builders already on Kontent.ai who want agent-driven CMS ops alongside code changes for docs, landing pages, or app copy.
Skip if: Greenfield projects not on Kontent.ai, or teams that only need read-only Delivery API fetches with no management actions.
What do I get? / Deliverables
After registration, your agent can list, create, and update Kontent assets through MCP tools while you stay in the editor.
- Agent-callable tools for Kontent content and type operations
- Faster CMS schema and entry changes aligned with code deploys
Recommended MCP Servers
Journey fit
Headless CMS work sits in Build when you connect the product’s content layer to shipping features and marketing sites. This is a Management API bridge—environment ID plus API key—ideal for the integrations slice of the builder journey.
How it compares
Kontent Management API MCP bridge, not a static content skill or a generic markdown CMS.
Common Questions / FAQ
Who is io.github.kontent-ai/mcp-server for?
Solo builders and small teams using Kontent.ai who want Claude Code, Cursor, or Codex to edit content models and entries from the terminal.
When should I use io.github.kontent-ai/mcp-server?
Use it in Build integrations when you are iterating content types, taxonomies, or workflows in the same week you ship site or app features.
How do I add io.github.kontent-ai/mcp-server to my agent?
Set KONTENT_API_KEY and KONTENT_ENVIRONMENT_ID, add @kontent-ai/mcp-server with positional stdio (or run shttp on port 3001), and reload your MCP client config.