--- title: Management MCP server related: - https://docs.kentico.com/documentation/developers-and-admins/api/management-api/reference-management-mcp-capabilities.md - https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md - https://docs.kentico.com/documentation/developers-and-admins/api/management-api/use-management-mcp-server.md --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). The **Management MCP server** is part of the [KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot.md) initiative, which brings AI-assisted development capabilities to the Xperience platform. The Management MCP server (formerly known as **Content types MCP server**) is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) server that works with any IDE, agent, or CLI tool that supports MCP. It connects to the management API in your local Xperience application and exposes its CRUD operations for Xperience objects as MCP tools that AI agents can discover and call. This enables AI-assisted management of Xperience objects such as content types, content items, pages, channels, languages, and more. It can be used to automate [content modeling](https://docs.kentico.com/guides/architecture/content-modeling.md) workflows, accelerate migration scenarios, and simplify integration with external systems. > **Tip:** You can use the Management MCP server to implement a model created by the [Content Modeling MCP Server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md). See [Prototype your model with Content modeling MCP server](https://docs.kentico.com/guides/development/kenticopilot/build-content-model-with-mcp.md) to learn more. ## How it works 1. You run your Xperience application locally with the Management MCP server [configured](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md). 2. Your IDE or AI client reads the MCP server configuration and starts the Management MCP server. 3. The MCP server reads the available operations from endpoints created by the management API. 4. The MCP server exposes those operations as MCP tools. 5. Your AI agent calls those tools when handling relevant prompts. The AI agent can then create, read, update, and delete supported objects, such as content types, content items, pages, channels, and more, through natural language prompts. See [Reference - Management MCP capabilities](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/reference-management-mcp-capabilities.md) for the full list of supported objects and tools, or [Use the Management MCP](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/use-management-mcp-server.md) for example prompts, CI guidance, and troubleshooting. ## Prerequisites - A local Xperience by Kentico instance (see [System requirements](https://docs.kentico.com/documentation/developers-and-admins/installation/system-requirements.md)). - [Node.js 22](https://nodejs.org/en/download) or newer (see [Task-specific requirements](https://docs.kentico.com/documentation/developers-and-admins/installation/system-requirements.md#task-specific-requirements)). - An IDE or AI client that supports the [Model Context Protocol](https://modelcontextprotocol.io/) (e.g., VS Code with GitHub Copilot, Claude Code, Cursor). ## Set up the Management MCP server See [Configure the Management MCP](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md) for steps to enable the management API, add the MCP server to your IDE, [limit available tools](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md#limit-the-available-tools), and [configure asset uploads](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md#configure-asset-uploads). ## Security limitations The management API is only intended for use on **local development instances**. It currently only provides basic authentication and no authorization options for various types of operations. Do **not** enable the management API for production deployments or other publicly available instances. ## Update policy and backward compatibility The Management MCP server and the underlying management API are designed to be operated by AI agents. For this reason, they are **not covered** by Kentico's standard [backward compatibility policy](https://docs.kentico.com/documentation/developers-and-admins/installation/support-policy.md#what-is-the-backward-compatibility-policy-for-features-and-code) and instead follow a more flexible set of rules: - The 12-month backward compatibility period is not guaranteed - Tools, API routes, and parameters can be removed or renamed without a transition period - Breaking changes can occur without advance notice Assume that the tool set and the API surface will be reworked and expanded often, including in weekly hotfix releases. All notable modifications are recorded in the product [Changelog](https://docs.kentico.com/changelog.md). The impact of changes on projects should be low, because agents can discover the current state of the server on their own and adapt. The tool list advertised by the MCP server and the [OpenAPI specification](https://swagger.io/specification/v3.2/) generated by the management API describe exactly what is available in the version you are running, and that description is authoritative. The OpenAPI specification is available under the _/kentico-api/management/v1/openapi.json_ URL path after the Management API is [enabled](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md#enable-the-management-api). > **Tip:** Use [Reference - Management MCP capabilities](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/reference-management-mcp-capabilities.md) as an overview of the covered objects and operations, but rely on your own instance when you need an exact answer. To limit the impact of updates on your projects: - Only **access the management API through an AI agent** rather than calling it directly (for example, from scripts). - Let agents read the available tools and routes from the MCP tool list and the OpenAPI specification instead of working from a fixed list. - Do not hardcode tool names in prompts or agent configuration. - Do not generate a client SDK from the OpenAPI specification. Such a client becomes outdated as soon as the API surface shifts. Kentico provides support for the Management MCP server and responds to reported issues. Because this area moves quickly, fixes and updates are delivered on a best-effort basis. The features are shaped by early feedback, so check the [product roadmap](https://roadmap.kentico.com/) to see what's coming and share your ideas.