The Content Modeling MCP Server helps you quickly move from business requirements to a prototype of a content model built on top of Xperience by Kentico content modeling practices.
It uses the Model Context Protocol (MCP) (opens in a new tab) to connect AI‑enabled clients (e.g., Claude Desktop or IDEs).
The server guides you through an orchestrated prompt flow: it captures requirements, proposes content types and relationships, suggests presentation components, and then validates the design before producing a JSON content model. That JSON becomes operational when you combine it with the Management MCP server, which you can use to programmatically create content types in Xperience, or build widgets or other Page Builder components that the content modeling server suggested.
Interesting, isn't it? Try the guided process yourself!
Configure and connect the MCP server in your environment using the Content modeling MCP Server documentation. To turn JSON models into real content types, explore the Management MCP server. Before running a large number of management API operations, review the recommended preparation for disabling CI and content versioning. And if you're new to the protocol itself, the Model Context Protocol (opens in a new tab) overview and specification (opens in a new tab) explain how MCP servers and hosts communicate.