Key Takeaways
- KentiCopilot's Management MCP Server now exposes over 100 tools to AI agents, up from a first release just months ago.
- Developers across the community are using KentiCopilot for real production work, not demos, from platform upgrades to building and launching websites.
- Three recent community posts show the range: C=content model designing, widget code generation, website Page Builder configuration, and E2E test creation.
- Recent Refreshes (Dec 2025 to Jul 2026) added Page Builder configuration and content managementsupport in the Management API/MCP server, a Kentico Xperience 13 content auditor CLI, and AI-assisted Kentico Xperience 13 to Xperience by Kentico upgrade tooling.
- The Xperience by Kentico AI Development Hub is a valuable, free resource for developers looking for KentiCopilot guidance and demo videos.
Already familiar with KentiCopilot, but don't know where to get started, or fear you're missing out on a helpful feature? If you're working in development, or hoping to inspire your development team with KentiCopilot use cases, this one's for you. Over the past several months, the community has been finding new ways to innovate with KentiCopilot's AI tools.
From content models to best practices, Kentico community guidance is a valuable resource for any development team looking to increase its impact on the next project.
1. Create new content types from an updated model
Did you know that you can install MCP servers into an existing project, enhance a content model with an AI agent, create new content types from that model, and generate a complex Page Builder widget from the resulting artifacts, all without leaving the editor?
One of the main improvements of this process is that widget-creation prompts no longer require cloning a GitHub repo as of the March 2026 Refresh.
They're now available as an installable skill straight from the plugin marketplace (located in kentico-web-development). Here's how developers are using it:
- Install the MCP servers into an existing Dancing Goat project as the starting point.
- Use an AI agent to enhance a content model, then generate new content types from it.
- Produce a complex, ready-to-use Page Builder widget without leaving the code editor.
This community blog gives a breakdown for inspired developers here that closes with a visual walkthrough of the marketer experience with the finished widget, showing how it works once the widget is available for use in content management.
2. Build and maintain widget catalogs with AI that you never have to touch
Here's a use case a lot of teams don't realize is possible: letting KentiCopilot document your project for you. You can generate a living widget catalog with KentiCopilot , built on the newly expanded Management MCP Server, which now hands AI agents 107 tools to work with. Ask your agent to inspect the implementation and find every registered widget, and it will spin up a whole browsable catalog on its own.
Try it out:
- Ask your agent to discover every registered widget in your Xperience by Kentico implementation.
- Have it build a dedicated section in the page tree with a rendered example page for each widget.
- Let it write the documentation itself; every configurable property, with a short description.
- Get a linked index page out of it, so the whole catalog is accessible for anyone on the team.
What used to be hours of busywork for QA engineers is now a five-minute prompt, resulting in a plain-language way for marketers to browse what's available before they ever open a ticket.
3. Lean on AI-supported Kentico Xperience 13 upgrades
Upgrades can be intimidating, so even when a platform is designed to be easy, extra support is always welcomed. KentiCopilot's Kentico Xperience 13 codebase migration support, detailed further in the January 2026 Refresh, pairs a documentation MCP server with the Playwright MCP server so your AI agent can crawl legacy Kentico Xperience 13 code, flag outdated patterns and methods, and rewrite them as Xperience by Kentico equivalents. It's complete with fully customizable prompts already built for Claude Code, and GitHub Copilot.
Here's how it works:
- Point an agent at your legacy Kentico Xperience 13 codebase and have it flag outdated patterns, methods, and APIs.
- Let it rewrite what it finds as modern Xperience by Kentico code, one step at a time, with you reviewing along the way.
- Combine the documentation MCP server with the Playwright MCP server for full context on your existing site.
- Use it alongside the broader Kentico Migration Tool already handling your content and commerce data migration.
If "we should upgrade eventually" has been sitting on your backlog, this is the use case for KentiCopilot that turns it into a scoped plan that makes you want to start tomorrow.
4. Conduct (reliable) automatic code checks
AI coding assistants don't inherently know Xperience by Kentico's APIs, and a generic suggestion can reference a method, type, or property that might not exist in the platform. KentiCopilot's documentation MCP server addresses this by giving an AI agent context about Xperience-specific patterns, so suggestions are more likely to match real APIs, and giving developers a way to check AI output against those conventions before merging it.
What developers are doing:
- Get code suggestions scoped to Xperience by Kentico's actual APIs and patterns, not generic framework guesses.
- Check AI-generated code against Xperience conventions before it goes into a project.
- Watch for a known failure mode of AI coding assistants: suggesting methods, types, or properties that don't exist in the platform.
- Apply this alongside any other KentiCopilot workflow, including widget generation or Kentico Xperience 13 migration.
Add the documentation MCP server to all of your Xperience by Kentico projects so AI agents can be expert advisors and implementors with knowledge of the latest features, APIs, and best practices.
5. Connect your project to an AI agent with MCP servers
An AI agent working in isolation only knows what's in its training data, likely leading to gaps in knowledge about Xperience by Kentico and your own project. KentiCopilot's MCP servers give developers a solution for this issue by connecting an agent directly to a project, so it can reference Kentico documentation, inspect the project's actual data, and carry out Kentico-specific operations.
Here is how this happens:
- Reference Kentico documentation directly from within an AI agent's context, instead of relying on outdated or incomplete training data.
- Analyze the existing project’s contentmodel and items (content types, content items, channels, pages) before generating or modifying anything.
- Execute Kentico-specific management operations in real time, letting agents work seamlessly across code and database.
- Work with whichever AI coding tool a developer already uses, since MCP servers are a well accepted standard in agentic software development.
This is the layer that the other workflows can build on, with greater accuracy. Without real-time project access, an agent is working from assumptions instead of the project in front of it.
What else can developers do with KentiCopilot?
These use cases are only the beginning. Outside of the Kentico Community blog, the Refresh notes over the past several months tell their own story about what's happening in KentiCopilot:
- Page Builder support was added to the Management API and Management MCP server, giving agents direct access to Page Builder components and data.
- A Kentico Xperience 13 content auditor CLI now snapshots a legacy database into structured JSON and a Markdown report, the starting point for an AI-assisted migration plan.
- Meanwhile the Management MCP server has kept growing, crossing the 100-tool mark and landing at 107 with the June 2026 Refresh.
- The Management MCP server was optimized further in the July 2026 Refresh to reduce context use and improve error messages for agents.
These updates are a direct benefit of Kentico's evergreen approach to updates: new AI tooling and updates are included according to the roadmap. Stay in the loop with updates by checking out Xperience by Kentico's roadmap, which includes any planned or released changes to KentiCopilot, like full agentic website development (link: https://roadmap.kentico.com/c/396-kenticopilot-agentic-website-development)
Beyond the Refresh notes and the Roadmap, the Learn Portal's KentiCopilot guides are the best single place to see everything the tooling covers today: MCP servers for real-time project integration, curated prompts built from Kentico development expertise, guidance for keeping AI-generated code aligned to Xperience conventions, and the KX13 codebase migration tooling, all laid out in one spot. If you're not sure where KentiCopilot fits into your own workflow yet, that's the place to start.
Get more out of AI-powered development
These three community stories, content-model-to-widget generation, automatic widget documentation, and the arrival of official Learn Portal guidance show KentiCopilot has quickly become an integral part of developer's workflows. An AI agent that understands Xperience by Kentico conventions innately can take on the repetitive, well-defined parts of a build, standing up content types, generating widgets, and documenting.
If you're looking for more inspiration and guidance beyond these community blogs, check out the Xperience by Kentico AI Development Hub. It's a treasure trove of helpful KentiCopilot resources, videos, integrations, articles, and community contributions that'll help developers hit the ground running with their next KentiCopilot powered project.
Frequently Asked Questions
Get ready for your upgrade
Upgrading from Kentico Xperience 13 to Xperience by Kentico gives your marketing and development teams a unified and future-proof platform with native AI that reduces complexity, and helps you create more impactful customer experiences.