Use the Management MCP

✖
Copy to clipboard

Preview feature

The Xperience by Kentico management API and Management MCP server are currently in preview mode. Expect changes in the functionality, potentially including breaking changes.

Feel free to try out the features, for example using the sample Dancing Goat project template. You can share your feedback directly with the Kentico Product team.

This page provides guidance on working with the Management MCP server, including example prompts, CI integration, content versioning behavior, and troubleshooting.

Use the MCP server

Once the Management MCP server is configured and running, your AI agent automatically discovers and uses the available tools when processing relevant prompts. You interact with the server through your AI agent’s interface.

For details on how MCP tools work within your specific environment, refer to the official documentation of your IDE or AI client, for example:

If Content versioning is enabled, each individual API call that modifies versioned content creates a separate version entry, which can lead to a long version history when performing a large number of operations.

Continuous Integration

Continuous Integration (CI) serialization is automatically disabled for all management MCP requests to prevent issues with concurrent file operations. After completing a logical group of changes (a task, feature, or workflow), run CI store manually to serialize the changes to the repository:

CMD
Manually store CI data 

dotnet run --no-build -- --kxp-ci-store

See Store object data to the repository for more details.

Upload assets

To create or update a content item with a Content item asset field, place your file in the configured asset upload directory and prompt the AI agent to create or update the content item using that file. The agent automatically handles the upload and references the asset in the content item.

Example prompts

Your AI agent can use the Management MCP server’s tools when handling prompts related to the supported objects. For example:

  • “List all content types containing a field with the ‘Content item asset’ data type.”
  • “Which content types use the ‘Product SKU’ reusable field schema?”
  • “Create a new workspace with code name ‘marketing_workspace’ and display name ‘Marketing workspace’.”
  • “List all project languages and add ‘French (France)’ as a new language, with the ‘fr-FR’ Formatting culture and English as the fallback language.”
  • “Create a new content type named ‘Coffee cup’ with fields ‘Size’, ‘Color’ and with the ‘Product SKU’ reusable field schema.”
  • “On the ‘Coffee Samples’ landing page, add a testimonial widget before the existing one.”
  • “Create a new content item of type ‘Article’ in the ‘News’ folder with the title ‘Product Launch’.”
  • “List all channels and their content type scopes.”
  • “Create a new page under the ‘About us’ section using the ‘Landing page’ content type.”
  • “Create a content item of type ‘Image’ and use sample.jpg as the file.”

Troubleshooting

Certificate issues

If your local application uses HTTPS and the MCP server reports certificate-related errors, configure Node.js to use the system certificate authority store.

Set the following environment variable in the MCP server configuration:

JSON
mcp.json – NODE_OPTIONS 

"env": {
    "MANAGEMENT_API_URL": "http://localhost:5001/kentico-api/management",
    "MANAGEMENT_API_SECRET": "<YourSecretValue>",
    "NODE_OPTIONS": "--use-system-ca"
}

Server does not start

If the Management MCP server does not start, make sure that:

Authentication fails or no tools are shown

If the MCP server starts but authentication fails or no tools appear, verify the following:

  • The local Xperience application is running and the management API is enabled.
  • MANAGEMENT_API_URL points to the correct local URL and includes the /kentico-api/management path.
  • MANAGEMENT_API_SECRET matches the secret configured in AddKenticoManagementApi() and has at least 32 characters.
  • Tool filtering options do not hide all tools.
  • Your AI client has been restarted after configuration changes.

Unexpected AI behavior

If the AI agent selects unrelated tools or produces unfocused results, try reducing the number of available tools:

  • Use --enabled-tools to expose only the tools needed for the current scenario.
  • Use --dynamic-tools to reduce the initial tool footprint.
  • Add project-specific AI instructions to guide the agent.
  • Ask the agent to summarize intended changes before executing them.

See Limit the available tools for configuration details.