Umbraco MCP Server & AI Connector
The Model Context Protocol is the open standard assistants use to reach outside tools. Umbraco AI Agent acts as an MCP server for your Umbraco site: the assistant asks it for a capability, it checks what you have authorised, and only then does it touch your site. This page covers the technical side for Umbraco.
Where this one stands
Umbraco has a Content Delivery API for reading and a Management API for writing, but the latter is documented through an OpenAPI document that production installations switch off. The same rule as Concrete applies: no building against a guessed payload.
Authentication and permissions
The assistant authorises through OAuth 2.1 with PKCE, and is granted scopes rather than an open door. Your Umbraco credential is encrypted at rest, tied to the one website it belongs to, and never sent to the assistant. Every operation is recorded, and an operation outside what you granted is refused before it reaches your site.
Common questions
What is an MCP server, in plain terms?
A service an AI assistant can call to do real work. Rather than describing a change to you, the assistant asks the server to make it. Umbraco AI Agent is that server for Umbraco, and the boundary of what it will do is set by what you authorised.
Does the assistant see my Umbraco password or token?
No. The credential is encrypted and bound to the single website it was given for, so a copy of it elsewhere is useless. The assistant asks for an action; it never receives the way in.
Is this an official Umbraco product?
No. Umbraco AI Agent is an independent product that uses Umbraco’s own published interfaces. It is not affiliated with or endorsed by Umbraco.
Getting started with Umbraco AI Agent
Umbraco AI Agent is not on sale yet. The product page tracks where it stands, and nothing is advertised before it works.