---
title: KentiCopilot
related:
  - https://docs.kentico.com/guides/development/kenticopilot/work-effectively-with-kenticopilot.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).

Building with Xperience by Kentico means holding a lot of context – platform APIs, project conventions, and your content model. **KentiCopilot** gives that context to the AI coding assistant you already use.

## 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 work more effectively with AI coding assistants when building with Xperience by Kentico.

> **Tip:** 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 with the _Xperience by Kentico_ platform. They work with any AI coding assistant that supports the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) and agent skills.

The following graph shows the available _KentiCopilot_ tools and resources.

![KentiCopilot tools and resources](https://docs.kentico.com/docsassets/guides/kenticopilot/kenticopilot_resources.png "KentiCopilot tools and resources")

## Add KentiCopilot into your project

Installing the tools is the first step. An agent also needs to know how your project is laid out, which conventions it follows, and how to verify its own changes. Without that context, every session starts over and the results vary.

### Install the KentiCopilot plugins

_KentiCopilot_ skills are distributed as [agent plugins](https://open-plugins.com/), and the [KentiCopilot repository](https://github.com/Kentico/xperience-by-kentico-kenticopilot) serves as the plugin marketplace. Each plugin installs separately, so you can add only the ones your work needs. The [usage guide](https://github.com/Kentico/xperience-by-kentico-kenticopilot/blob/main/docs/Usage-Guide.md#install-the-selected-plugin) in the repository lists the available plugins and the detailed installation steps.

Add the marketplace to your coding assistant, then install a plugin by name. For example, in Claude Code:

```text title="Install the web development plugin"
/plugin marketplace add Kentico/xperience-by-kentico-kenticopilot
/plugin install kentico-web-development@xperience-by-kentico-kenticopilot
```

The commands differ between AI tools. See the usage guide for the equivalent steps in yours.

### Check your project's readiness

The `agentify` skill in the [web development plugin](https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kentico-web-development) audits an existing project against Kentico's agentic-development practices. The skill asks which AI tool you work with, evaluates the project, and writes a readiness report that names each gap. Nothing in your repository changes until you approve the recommendations.

To run the audit, you need an Xperience by Kentico project and the web development plugin. Then ask your assistant to run the `agentify` skill against the project in your workspace.

The audit evaluates your project in a few areas:

- Agent instructions
- Design and coding standards guidance
- [Documentation](https://docs.kentico.com/documentation/developers-and-admins/installation/mcp-server.md) and [Management](https://docs.kentico.com/documentation/developers-and-admins/api/management-api/configure-management-mcp-server.md) MCP server configuration

With your approval, the skill then creates the missing files and places them where your AI tool discovers them.

A project that passes the audit gives every new session the same starting context, which makes the results of the other [curated skills and workflows](#curated-skills-and-workflows) more consistent.

With the project prepared, see [Work effectively with KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot/work-effectively-with-kenticopilot.md) for the habits that get the most out of the tools.

## 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](https://github.com/Kentico/xperience-by-kentico-kenticopilot) specifically optimized for Xperience by Kentico development scenarios.

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

- [Prototyping your content model](https://docs.kentico.com/guides/development/kenticopilot/build-content-model-with-mcp.md), including content types, taxonomies, and Page Builder components.
- [Developing Page Builder widgets](https://docs.kentico.com/guides/development/kenticopilot/implement-widgets-kenticopilot.md), sections, and page templates.
- [Building custom modules](https://community.kentico.com/blog/dream-and-experiment-building-a-component-registry-dashboard-with-ai) and integration scaffolding built on top of real-life examples.
- [Analyzing of content types and their relationships](https://docs.kentico.com/guides/development/kenticopilot/analyze-content-type-relationships.md) and programmatic content types creation.

### AI-assisted web development

The [web development plugin](https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kentico-web-development) covers a design-led implementation end to end: preparing the project for agentic development, modeling content from a design, building [Page Builder widgets](https://docs.kentico.com/guides/development/page-builder.md), sections, and page templates, writing content retrieval code, and comparing the finished implementation against the original design.

Before generating any code, these skills study the components your project already has, mirror your repository's conventions, and verify uncertain APIs against the current Xperience documentation.

**Development capabilities:**

- **Generated artifacts**: Content types and [reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) derived from a design. Page Builder widgets, sections, and page templates with their views, properties classes, and localized resources. Content retrieval code for the models you build. If your repo already has components, 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 and APIs, respective documentation pages, or example components to help the agent identify implementation patterns.
- **Best practices** for the components you build, with examples and customization ideas.

Check out a video series where _KentiCopilot_ powers a full widget build. See how AI automates content modeling and creates a ready-to-use [Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md) widget in [Build Smarter: From Content Model to Widget with KentiCopilot](https://community.kentico.com/blog/build-smarter-from-content-model-to-widget-with-kenticopilot).

### KX13 upgrade hands-on assistance

_KentiCopilot_ includes specialized tooling to help you [migrate](https://docs.kentico.com/guides/upgrade-to-xbyk.md) legacy Kentico Xperience 13 (KX13) projects to Xperience by Kentico. The [KX13 migration plugin](https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kentico-kx13-migration) covers the full upgrade journey in a single plugin, organized into groups of skills:

- **Content-model audit** – Pairs an AI skill with a bundled .NET CLI that snapshots a KX13 database into structured JSON and a Markdown report. The output is the canonical input for the migration plan.
- **Content migration** – Turns the audit into a migration plan, generates the [Kentico Migration Tool](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool) `appsettings.json` and the C# extensions for `Migration.Tool.Extensions`, executes the migration tool, and evaluates the result. The eval skill produces an HTML report that classifies each finding and routes back to the specific sibling skill to re-run.
- **Codebase migration** – Sets up the XbyK project foundation, migrates page controllers and views to the new [content retrieval API](https://docs.kentico.com/documentation/developers-and-admins/api/content-item-api/content-retriever-api.md), migrates Page Builder widgets and shared components, and reconciles visual differences between original and migrated pages with Playwright.

**Upgrade capabilities:**

- **Source content audit**: Snapshots the KX13 content model into structured JSON, giving the rest of the skills a deterministic input.
- **Migration plan generation**: Decides content-type strategy and migration tool configuration from the audit – content hub conversions, reusable field schemas, linked-page handling, widget transforms.
- **Automated code analysis**: Scans the KX13 codebase to identify APIs, patterns, and dependencies that require updates.
- **Pattern Transformation**: Converts legacy code patterns to XbyK equivalents with AI assistance.
- **Iterative loop**: Treats configure → codegen → run → eval as one loop. The eval skill names the specific sibling skill to re-run for each finding.
- **Incremental migration**: Supports gradual migration in manageable steps – feature-by-feature, page-by-page.

### Project lifecycle maintenance

Once a project is in production, the [project lifecycle plugin](https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kentico-project-lifecycle) helps you keep it current and deploy changes in a controlled way:

- `update-xperience` – Determines your current and target Xperience versions, reviews every [Changelog](https://docs.kentico.com/changelog.md) entry in between together with the update guides they link to, and then follows the official [update procedure](https://docs.kentico.com/documentation/developers-and-admins/installation/update-xperience-by-kentico-projects.md).
- `cd-repository-configure` – Builds deployment-scoped [repository.config](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md) filters from the pull requests or commit range you want to deploy, excluding Xperience version-only changes, and then exports and verifies the serialized deployment content.

### Digital experience extensions

The [digital experience plugin](https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kentico-digital-experience) enables coding assistants to develop [custom components](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/automation-customization.md) for [automation processes](https://docs.kentico.com/documentation/business-users/digital-marketing/automation.md). Its skills implement and register custom automation steps and triggers, which marketers can use and configure in the Automation Builder.

## MCP servers

[Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/learn/server-concepts) 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.

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.

### 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](https://docs.kentico.com/documentation/developers-and-admins/installation/mcp-server.md) to learn more.

### Content Modeling MCP server

Provides content modeling assistance with validation and best practice checks. See [Content Modeling MCP Server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md) to learn more.

### Management MCP server

Provides integration with the Xperience by Kentico management API to allow querying and editing of content, configuration, and other objects stored in the system's database. This includes the project's content model (content types and reusable field schemas), content items, pages (including [Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md) content and configuration), channels, languages and more.

See the [Management MCP server](https://docs.kentico.com/documentation/developers-and-admins/api/management-api.md) documentation for more information and instructions.

### Open-source MCP servers and libraries

We've built and open-sourced the following tools to help you deliver your projects more easily:

- [Virtual Inbox MCP server](https://github.com/Kentico/xperience-by-kentico-virtual-inbox) – 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](https://github.com/kentico/xperience-by-kentico-component-registry) – 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](https://community.kentico.com/blog/dream-and-experiment-building-a-component-registry-dashboard-with-ai) to learn how and why we built this module.
- [Annotated Kentico icons library](https://github.com/kentico/xperience-by-kentico-component-icons) – This is a ready-to-use, annotated list of all icons used in Xperience by Kentico [Page](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md), [Email](https://docs.kentico.com/guides/development/email-marketing/email-builder-overview.md), and [Form Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/form-builder.md) 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](https://community.kentico.com/blog/smarter-components-using-icon-metadata-to-guide-ai-in-kentico-projects).
- [Admin UI Design Components](https://github.com/Kentico/xperience-by-kentico-admin-design-components) – A modified reference library for the React components that power the Xperience by Kentico administration UI, which gives AI agents component design context when generating admin UI extensions.

### Custom MCP servers

In addition to the official Kentico MCP servers that provide out-of-the-box functionality, you can create your own tooling, such as custom MCP servers and other toolsets:

- Apply 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.

The official Kentico MCP servers are compatible with third-party MCP servers, so you can extend the current functionality with your own servers or integrate other tools into your development workflow.

## Learn AI-assisted development fundamentals

_KentiCopilot_ works best when you are comfortable directing an AI coding assistant. If you are new to AI-assisted development, start with the general fundamentals. The same habits apply to every assistant: plan before you generate code, provide specific context instead of vague prompts, and review everything the assistant produces.

The following free resources assume little or no prior AI knowledge:

- [Anthropic Academy](https://www.anthropic.com/learn) – Free self-paced courses, ranging from everyday AI assistant usage to developer topics such as MCP and agent skills.
- [AI Fluency: Framework & Foundations](https://anthropic.skilljar.com/ai-fluency-framework-foundations) – Teaches the four core competencies of working with AI: Delegation, Description, Discernment, and Diligence. Suitable for any role.
- [Claude Code best practices](https://code.claude.com/docs/en/best-practices) – Explains how to explore and plan before coding, provide specific context in prompts, and delegate investigation to subagents. The principles transfer to other agentic coding tools.
- [How an agent remembers your project](https://code.claude.com/docs/en/memory) – Shows how persistent instruction files, such as `AGENTS.md`, give an assistant project context across sessions.
- [GitHub Spec Kit](https://github.com/github/spec-kit) (advanced) – A toolkit for spec-driven development. You describe what to build in a specification, and the assistant derives the plan, tasks, and code from it. Works with GitHub Copilot, Claude Code, and other agents.

Kentico-specific materials build on those fundamentals. You can find them in the Xperience by Kentico [documentation](https://docs.kentico.com/documentation.md), in the developer [guides](https://docs.kentico.com/guides/development.md), or in blog posts on the [Community Portal](https://community.kentico.com/blog):

- [Step-by-step guidance](https://github.com/Kentico/xperience-by-kentico-kenticopilot/blob/main/docs/Usage-Guide.md) for installing the plugins and invoking their skills.
- Conceptual [guides](https://docs.kentico.com/documentation/developers-and-admins/api/management-api.md) explaining how _Xperience by Kentico MCP servers_ work and how you can [put them to work](https://community.kentico.com/blog/ship-faster-modeling-content-and-widgets-with-ai-in-xperience-by-kentico#crafting-a-content-model-from-design).
- [Migration guides](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-deep-dives/speed-up-remodeling-with-ai.md) for adopting AI-assisted development in existing projects.
- [Query and data retrieval patterns](https://community.kentico.com/blog/ship-faster-modeling-content-and-widgets-with-ai-in-xperience-by-kentico) based on Kentico documentation and API examples.

Once you know the fundamentals, the _KentiCopilot_ [curated skills and workflows](#curated-skills-and-workflows) apply them to Xperience by Kentico scenarios, so you do not need to design your own prompts and workflows from scratch.

> **Tip:** For a comprehensive collection of AI-assisted development resources, including articles, videos, and community contributions, visit the [Xperience by Kentico AI Development Hub](https://community.kentico.com/resource-hub/xperience-by-kentico-ai-development-hub) on the Community Portal.

## AI tool compatibility

_KentiCopilot_ is built on open standards, primarily the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) and agent skills. This means you're not locked into a specific AI tool, and no specific tool or editor is required. See [System requirements](https://docs.kentico.com/documentation/developers-and-admins/installation/system-requirements.md#ai-tool-compatibility) for more information.

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

KentiCopilot's [curated skills and workflows](#curated-skills-and-workflows) use plugin architecture, which allows quick installation specifically in Claude Code and GitHub Copilot environments.

> **Note:** Results may vary depending on the AI model and client. For best results, use a recent flagship model together with a commonly used MCP-compatible AI development tool.

## KentiCopilot guides and videos

### Working with KentiCopilot

- [Work effectively with KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot/work-effectively-with-kenticopilot.md) **CONCEPT** – Learn the habits that get better results from any AI tool: explore before coding, delegate investigation to subagents, give specific context, and verify the result against the running site.
- [Build a website with KentiCopilot](https://docs.kentico.com/guides/development/developer-kickstart/build-a-website-with-kenticopilot.md) **CONCEPT** – Watch a whole website get built with an AI coding assistant: a specification written from your own source material, then the content model, demo content, and presentation layer implemented against it. See what the assistant handled, and where the decisions stayed with the developer.

### Documentation access

- [Documentation MCP server](https://docs.kentico.com/documentation/developers-and-admins/installation/mcp-server.md) – 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 is compatible with any IDE or AI client that supports MCP.

### Content type management

- [Analyze content type relationships](https://docs.kentico.com/guides/development/kenticopilot/analyze-content-type-relationships.md) **HOW-TO** – Use your agentic coding assistant to generate a concise summary of content types and their relationships.

### Widget implementation

- [Rapidly implement widgets with KentiCopilot](https://docs.kentico.com/guides/development/kenticopilot/implement-widgets-kenticopilot.md) **HOW-TO** – Watch a five-minute demo showing widget implementation from start to finish, then use the detailed skills and requirements templates from the _KentiCopilot_ repository to build your own widgets with AI assistance.
- [Implement product display patterns with KentiCopilot](https://docs.kentico.com/guides/development/commerce/product-display-patterns-kenticopilot.md) **CONCEPT** – Examine key considerations for rapidly creating product display widgets with KentiCopilot's plugins and skills.

### Remodeling during upgrades

- [Speed up remodeling with AI](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-deep-dives/speed-up-remodeling-with-ai.md) **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

- [Content Modeling MCP Server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md) **CONCEPT** – Learn how to use the _Content Modeling MCP server_ to speed up content model creation with a structured workflow and built-in validation against Kentico best practices. The MCP server is compatible with any IDE or AI client that supports MCP.

- [Prototype your model with Content modeling MCP server](https://docs.kentico.com/guides/development/kenticopilot/build-content-model-with-mcp.md) **CONCEPT** – See how you can use the [Content Modeling MCP server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md) together with the [Management MCP server](https://docs.kentico.com/documentation/developers-and-admins/api/management-api.md) to rapidly prototype a content model for your project. Learn how to speed up model creation, iterate faster, and keep everything consistent across your solution.

### Community case studies

- [AI assisted improvements to the Kentico Community Portal](https://community.kentico.com/blog/ai-assisted-improvements-to-the-kentico-community-portal) – Learn how GitHub Copilot was used to accelerate UI improvements, search redesign, and Q\&A tagging on a real in-production Xperience by Kentico project.

- [Can AI really update my Xperience by Kentico project?](https://community.kentico.com/blog/can-ai-really-update-my-xperience-by-kentico-project) – Explore an AI-driven workflow for automating Xperience by Kentico hotfix and refresh updates, including package changes, database migrations, and breaking change resolution.

- [AI-Powered Refactoring: Updating Xperience by Kentico Logging with a Single Prompt](https://community.kentico.com/blog/ai-powered-refactoring-updating-xperience-by-kentico-logging-with-a-single-prompt) – See how a single GitHub Copilot prompt, backed by the Documentation MCP server, migrated the entire Kentico Community Portal from `IEventLogService` to `ILogger<T>`.

- [Deliver More: AI Assisted Improvements to Q\&A Discussions](https://community.kentico.com/blog/deliver-more-ai-assisted-improvements-to-q-a-discussions) – Discover how AI expanded the scope of Community Portal improvements, including discussion notifications, timezone customization, and reaction voting, without increasing development time.

- [Smarter Components: Using Icon Metadata to Guide AI in Kentico Projects](https://community.kentico.com/blog/smarter-components-using-icon-metadata-to-guide-ai-in-kentico-projects) – Learn how AI-generated descriptions added to Kentico's icon class help AI agents select the right icon when generating Page Builder component registrations.

## 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. 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, but not turning it into an autonomous stand-in for developers.

**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 back-end and front-end development:

- C#/.NET back-end development of [ASP.NET Core](http://ASP.NET) applications, custom modules, integrations.
- JavaScript/TypeScript front-end development, including Xperience by Kentico React components.