xperience-community

This MCP server is delivered as a NuGet package (XperienceCommunity.MCPServer) designed to integrate with Xperience by Kentico projects. It exposes a focused set of MCP tools accessible to an AI agent running inside a developer’s Xperience application, enabling structured context and capabilities for content modeling and management tasks. The server is intended to be added to your application, then activated in development so that the MCP endpoints and tools can be used within VS Code’s MCP client for agent-assisted workflows.

Prerequisites:

• .NET 8.0 SDK or later
• A Xperience by Kentico project where you can integrate the MCP server
• Visual Studio Code with MCP Server support (and a dev certificate if using HTTPS)

Step 1: Add the MCP server package to your project

dotnet add package XperienceCommunity.MCPServer

Step 2: Enable the MCP server in your application during development

// Program.cs

// Adds the MCP dependencies
if (builder.Environment.IsDevelopment())
{
    builder.Services.AddXperienceMCPServer();
}

// Adds the MCP endpoint
if (builder.Environment.IsDevelopment())
{
    app.UseXperienceMCPServer();
}

app.Kentico().MapRoutes();

Step 3: Launch your Xperience by Kentico application and verify the MCP endpoint is active (default path is typically /xperience-mcp for the MCP server).

Step 4: Configure MCP in VS Code

{
  "servers": {
    "xperience-mcp-server": {
      "type": "http",
      "url": "http://localhost:<your-port-here>/xperience-mcp"
    }
  }
}

Note: VS Code MCP client requires http bindings if you are avoiding HTTPS in development. See the README for more details on launchSettings and dev-certs.

Notes:

• This MCP server package was deprecated in favor of native Xperience capabilities; consider using the Content Type Management API, Documentation MCP server, or Content Modeling MCP Server provided by Kentico for new projects.
• The MCP tooling is designed to run within a .NET application, not as a standalone process. Ensure your launchSettings and http bindings are configured correctly for MCP access in VS Code during development.
• If you encounter issues with self-signed certificates in VS Code, bind to http (not https) for local development and update mcp.json accordingly.
• The NuGet package is distributed under the MIT License; refer to LICENSE.md for details.