Documentation MCP server

The Xperience by Kentico Documentation MCP Server allows AI agents to securely access complete and up-to-date documentation, including guides and API examples. The MCP server provides guidance for all areas of Xperience by Kentico, for example content management, digital marketing, or digital commerce, directly within your integrated development environment (IDE).

The MCP server is built on the Model Context Protocol (MCP), an open standard that lets clients dynamically discover and query external data sources in real time. The server provides accurate, context-aware responses by combining semantic search with high-quality content retrieval from the official documentation in markdown format. Since the server syncs continuously with the published documentation, you’ll always get the most recent information and implementation details available.

Install the MCP server

The MCP server supports quick installation across multiple IDEs. Choose your preferred client below for a streamlined setup:

Example: Add the MCP server to VS Code

Before adding the MCP server to your VS Code, make sure you have set up the GitHub Copilot.

1. Open GitHub Copilot in VS Code and switch to Agent mode.
2. Select Configure Tools in the right bottom corner of the chat window, next to the Send button.
3. Check the box next to the MCP Server: kentico.docs.mcp.
4. The agent should be able to use the MCP server tools to complete your query.

The Xperience by Kentico MCP server endpoint

The Xperience by Kentico MCP Server is accessible to any IDE, agent, or tool that supports the Model Context Protocol (MCP). Any compatible client can connect to the following remote MCP endpoint: https://docs.kentico.com/mcp.

{
  "kentico.docs.mcp": {
    "type": "http",
    "url": "https://docs.kentico.com/mcp"
  }
}

If your client doesn’t support native remote MCP servers or if you prefer local configuration, you can use mcp-remote as a proxy. Configure MCP servers in .mcp.json at your project root.

{
  "mcpServers": {
    "remote-example": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://docs.kentico.com/mcp"
      ]
    }
  }
}

MCP server tools

In the context of the MCP server, tools are individual capabilities that the MCP server exposes to connected clients (for example GitHub Copilot, Claude, or Cursor). Each tool performs a specific function, such as searching or fetching, and can be called programmatically by the client when it needs information from the server.

The MCP server currently provides two tools that let AI agents access official Kentico documentation:

Example prompts

Your AI assistant should automatically use these tools for Xperience by Kentico-related topics. With both search and fetch capabilities, you can get quick answers or comprehensive deep dives. To ensure that it always consults the official documentation, you can add phrases like search Kentico docs, use XbyK docs, fetch full Xperience docs. For example:

• “How do I create a custom page type in Xperience by Kentico? Search Kentico docs.”
• “Are you sure this is the right way to implement custom form components in Xperience by Kentico? Search Kentico docs and fetch full doc.”
• “Get me the full step-by-step tutorial for setting up multi-site management. Search Kentico docs and deep dive.”

Troubleshooting

If the MCP Server isn’t responding as expected or the tools don’t appear in your environment, the following guidance can help resolve common issues quickly.

Ensure AI clients use MCP tools

Some AI clients, such as Claude or GitHub Copilot, may not automatically use MCP tools when answering Kentico-related queries. To improve reliability, you can define a system prompt that explicitly tells the client to use the Xperience by Kentico MCP tools.

Here’s an example of a Cursor rule (a system prompt) that will cause the LLM to utilize kentico.docs.mcp more frequently:

Common Issues