KentiCopilot

As a developer building digital experiences with Xperience by Kentico, you know productivity thrives when you stay in flow. Constantly switching between tools and searching documentation slows down development. That’s why we created KentiCopilot.

Meet KentiCopilot

KentiCopilot is a suite of AI development tools that enables agentic development for Xperience by Kentico projects. It combines MCP (Model Context Protocol) servers, curated skills and workflows, and best practices to help developers leverage AI coding assistants more effectively when building with Xperience by Kentico.

Think of KentiCopilot as an umbrella term for all the tools, features, instructions and built-in guidance we provide to help developers work smarter with AI.

Instead of acting as a standalone AI agent, KentiCopilot tools bridge your preferred AI development tools, such as GitHub Copilot, Cursor, Claude Code, or Codex, with the Xperience by Kentico platform.

Key KentiCopilot components

The KentiCopilot tools include three main components that together deliver a powerful AI-assisted development experience.

The following graph shows the available KentiCopilot tools and resources.

KentiCopilot tools and resources

MCP servers

Model Context Protocol (MCP) servers are the foundation of KentiCopilot’s capabilities. These servers expose Xperience by Kentico functionality directly to AI assistants and enable them to interact with your projects, access documentation, and execute Kentico-specific operations in real time.

Documentation MCP server

Provides access to Xperience by Kentico documentation and code examples. Serves as a reliable source of context for your agentic workflows. See Documentation MCP server to learn more.

Content Modeling MCP server

Provides content modeling assistance with validation and best practice checks. See Content Modeling MCP Server to learn more.

Content types MCP server

Provides integration with the Xperience by Kentico management API to allow querying and editing of the system’s object model, data structures, and configuration. See the Content types MCP server documentation for more information and instructions.

Purpose-built MCP servers

In addition to the official Kentico MCP Servers that provide out-of-the-box functionality, you can create your own MCP servers to meet specific needs:

  • Leverage custom business logic and domain- or agency-specific operations.
  • Integrate with your organization’s internal tools and systems.
  • Provide access to project-specific shortcuts and automation workflows.
  • Promote agency-specific or team-specific conventions and patterns.

MCP servers use a standardized protocol that allows AI assistants to discover available capabilities, understand their parameters, and execute operations safely within your development environment. We’ve built and open-sourced these MCP servers to help you deliver your projects more easily:

  • Virtual Inbox MCP server – An in-app hosted virtual inbox for email channel development, testing, and AI agent email access. You can use it when you need AI agents to validate email content and rendering after code changes, drive end-to-end testing of visitor journeys, such as automations and membership experiences, or run demo environments that need email “delivery” without a real SMTP inbox.
  • Component Registry MCP server – This custom module lets administrators see all registered custom components in an Xperience by Kentico app, like Page Builder widgets. It also shows which channels and web pages use each component through an admin interface. Read the blog post to learn how and why we built this module.
  • Annotated Kentico icons library – This is a ready-to-use, annotated list of all icons used in Xperience by Kentico Page, Email, and Form Builder components. It helps AI agents avoid making up icons when building Xperience components. To learn more about why we created this library, check out the article Smarter Components: Using Icon Metadata to Guide AI in Kentico Projects.

Curated skills and workflows

Effective AI-assisted development requires more than just access to tools. The KentiCopilot tools include a growing library of skills and plugins specifically optimized for Xperience by Kentico development scenarios.

Pre-built skills and orchestrated workflows help you with common development tasks:

AI-assisted widget development

A two‑stage workflow for building widgets walks you through creating Xperience Page Builder widgets. The workflow includes a Research stage where the AI agent analyzes your requirements and optional design, validates them against official Xperience docs, and generates a detailed, project‑aware implementation plan. The Implementation stage then converts that plan into production‑ready widget code that follows your repository’s conventions and mirrors patterns from existing widgets.

Development capabilities:

  • Generated artifacts: View component class, widget properties class, Razor view (.cshtml), view model, and localized resources (.resx + registration if needed). If your repo already has widgets, the output mirrors your existing filesystem layout and coding patterns.
  • Context files: Shipped alongside the skills, they instruct the agent to look for specific resources and information, such as core concepts & APIs, respective documentation pages, or example widgets to help the agent identify implementation patterns.
  • Best practices for building widgets, examples, and customization ideas.

KX13 code upgrade hands-on assistance

KentiCopilot includes specialized tooling to help you migrate legacy Kentico Xperience 13 codebases to Xperience by Kentico. The AI-assisted codebase migration helps transfer legacy files between projects and update KX13 legacy code to support XbyK data retrieval practices.

Migration capabilities:

  • Automated Code Analysis: Scans your Kentico Xperience 13 (KX13) codebase to identify APIs, patterns, and dependencies that require updates.
  • Pattern Transformation: Converts legacy code patterns to XbyK equivalents with AI assistance.
  • API Mapping: Identifies deprecated APIs and suggests replacements from the XbyK API.
  • Incremental Migration: Supports gradual migration that allows you to modernize your project in manageable steps, e.g., porting the solution in feature-by-feature steps.

Check out a six-video demo where KentiCopilot powers a full widget build. See how AI automates content modeling and creates a ready-to-use Page Builder widget in Build Smarter: From Content Model to Widget with KentiCopilot.

Best practices in educational materials

Together with KentiCopilot we provide comprehensive educational resources to help developers effectively and safely leverage AI assistants in Xperience development. You can find various materials in the Xperience by Kentico documentation, in different developer guides, or in blog posts on Community Portal.

We are (and will be) creating:

For a comprehensive collection of AI-assisted development resources, including articles, videos, and community contributions, visit the Xperience by Kentico AI Development Hub on the Community Portal.

Which tools does KentiCopilot support

KentiCopilot aims to create flexible tooling, which means you’re not locked into a single AI tool. The tools we’ve built work with common AI development tools that developers already use.

Examples of supported AI tools

  • Visual Studio/Visual Studio Code: Compatible with AI extensions, including GitHub Copilot, ClaudeCode, Codex, and other MCP-enabled extensions that bring AI assistance directly into your IDE.
  • Cursor IDE: Full MCP support enables KentiCopilot through your development workflow.
  • GitHub Copilot: Works with KentiCopilot skills and guidance to generate Kentico-specific code suggestions.
  • Claude Desktop: Native MCP integration provides the seamless KentiCopilot experience, especially for content model prototyping.
  • Other MCP-Compatible Tools: Any AI assistant that implements the Model Context Protocol can leverage KentiCopilot’s capabilities.

You can combine multiple tools to support project implementation; for example, leverage Claude Code for complex, multi-step tasks and GitHub Copilot for inline code suggestions.

As new AI development assistants emerge, KentiCopilot’s MCP and skill-based architecture ensures compatibility without major changes to your workflow.

KentiCopilot guides and videos

Documentation access

  • Documentation MCP server – Learn how to install the Documentation MCP server to provide your AI assistant with real-time access to Kentico documentation through semantic search and content retrieval. The MCP server supports VS Code, Visual Studio, Claude Desktop, and Cursor.

Content type management

  • Analyze content type relationships HOW-TO – Use your agentic coding assistant to generate a concise summary of content types and their relationships, rather than manually clicking through dozens of content types and their fields to learn how they relate.

Widget implementation

Remodeling during upgrades

  • Speed up remodeling with AI CONCEPT – See how agentic AI coding assistants can accelerate the process of remodeling content types and field mappings during your upgrade. Learn how to provide the best context and instructions for the highest quality results.

AI-powered content modeling

Community case studies

More materials coming soon!

KentiCopilot FAQs

Is KentiCopilot an AI agent?

No, KentiCopilot is not an AI agent itself. It’s a suite of tools that enables developers by enhancing 3rd-party AI assistants (like Claude Code or GitHub Copilot). The tools developed under the KentiCopilot umbrella provide AI assistants and agentic coding tools with specialized knowledge and capabilities for Xperience by Kentico development. Think of the KentiCopilot tooling as giving your AI assistant expert-level knowledge of Kentico rather than being an autonomous agent.

Is KentiCopilot an MCP server?

No, but MCP servers are a core component of tools developed under the KentiCopilot umbrella. Xperience MCP servers act as a bridge, allowing AI assistants to access Xperience-specific information and interact directly with your Kentico projects.

The official Kentico MCP servers expose Xperience by Kentico functionality to AI assistants. They are compatible with other 3rd-party MCP servers, so you can extend current functionalities with your own custom servers or integrate other tools in your development workflow.

Is KentiCopilot a skill or a plugin?

No, but curated skills are a key feature. As a part of KentiCopilot, we have been creating:

  • Skill definitions that are optimized for common Kentico development tasks.
  • System prompts to give AI assistants context about Xperience by Kentico architecture and best practices.
  • Reusable skill files for code generation, troubleshooting, and content modeling.
  • Guidelines for crafting effective instructions specific to Kentico development scenarios.

Is KentiCopilot supported by any educational guidance and tutorials?

Yes, we back KentiCopilot with comprehensive education to ensure your AI implementation is a success. To help you master these tools, we provide a growing library of resources:

  • Step-by-step tutorials for setting up AI-assisted development workflows.
  • Documentation on how to effectively use AI for Kentico development.
  • Examples and use cases demonstrating best practices.
  • Learning resources for developers new to AI-assisted development.

Does KentiCopilot provide any practical recommendations for AI + Xperience development?

Absolutely. KentiCopilot embodies and teaches best practices including:

  • Secure coding patterns when using AI-generated code.
  • Architectural guidance aligned with Xperience by Kentico conventions.
  • Code quality standards and review processes for AI-assisted development (upcoming)
  • Performance optimization strategies (upcoming).
  • Testing and validation approaches for AI-generated implementations (upcoming).

Are KentiCopilot tools locked to a specific AI development tools/editors?

No, KentiCopilot supports multiple AI development tools and coding agents. We are optimizing KentiCopilot tools for the following:

IDEs

  • VS Code / Visual Studio 2022/2026 (with AI extensions)
  • Cursor
  • Claude Code (CLI)

Agents

  • GitHub Copilot
  • ClaudeCode
  • Codex

The MCP-based architecture ensures KentiCopilot can work with any AI tool that supports the Model Context Protocol.

Is KentiCopilot tooling for C#/.NET only, or does it include also JavaScript/React?

The toolkit recognizes that Xperience by Kentico projects often involve both server-side and client-side code. Tools built under the KentiCopilot umbrella support both backend and frontend development:

  • C#/.NET backend development of ASP.NET Core applications, custom modules, integrations.
  • JavaScript/TypeScript frontend development, including Xperience by Kentico React components.