Umbraco Cloud Now Hosts Editor and Developer MCP Servers

Content Management AI/ML News

Earlier this month we looked at how Sitecore, Webflow and Sanity opened MCP paths for coding agents, each with different rules for who can write. Today the story moves to the editor's chair. This week, Umbraco's Bolette Kern says the company's CMS Editor MCP and CMS Developer MCP are officially live as remote servers hosted on Umbraco Cloud. The Editor MCP had been in public beta. 

The question is what that access means when a write can be a draft, a publish, or a schema change.

What Each MCP Can Reach

The CMS Editor MCP is aimed at editors and marketers, in the AI clients they already use. Official docs and the announcement describe tools to find, create, edit, publish and organize pages, including block editors and drafts; upload and move media; manage translations and members; and check content health, such as stale pages, SEO issues, and incoming links before a delete. It stays out of Settings: it cannot change document types, data types or templates, and it cannot manage users. Docs also describe bulk publish, unpublish, move and update operations. Site-wide Global Actions are on the public roadmap, not shipping today.

The CMS Developer MCP is the server developers already used locally, now also hosted. Umbraco says it covers nearly everything in the backoffice, including Settings and Users. The local npx path remains. Official Developer MCP documentation is still written around that local setup, and it still warns teams not to connect the Developer MCP Server to a production environment. The November 19 post does not lift that warning for the hosted Cloud URL. Until the docs change, teams should treat it as still in force.

Setup, as documented, is a one-time install of the Umbraco.Mcp.HostedAuth package on the Cloud project, then a deploy. Official Cloud quick start docs say to pin the package to the matching Umbraco major, for example 18.*. Each project then gets a remote URL such as https://cms.editor.18.mcp.umbraco.ai/at/{alias}.{region}/mcp, with developer in place of editor for the Developer MCP, and with major versions 17 or 18. Supported clients in the docs include ChatGPT, Claude.ai, Claude Desktop, Cursor, Visual Studio Code, Claude Code, GitHub Copilot and OpenAI Codex. Umbraco says the CMS Editor MCP is free on all Umbraco Cloud plans, and that a self-hosted path is also documented. The announcement does not state a separate price for the hosted Developer MCP. Forms, Engage and Automate MCPs are planned for Cloud hosting in the first quarter of 2027, a vendor roadmap.

How Access Is Governed

On the hosted path, the MCP authenticates with OAuth as the signed-in Umbraco backoffice user. Official docs say the tools available are determined by that person's own permissions: if you can do it in the backoffice, you can do it through the CMS Editor MCP. There is no tool picker for the user; the tools are already scoped to those permissions. Admins can further restrict tools server-side. The local stdio path is different: it authenticates as a fixed API user, so access follows that account, not the person at the keyboard.

Write actions are "designed to be confirmed before they run," Umbraco says, but "this depends on your client," including for bulk operations. That is not a product-enforced gate we have verified. If the client skips the prompt, or a user allows the action for the rest of the conversation, a person with publish rights has given an agent publish rights. We also did not find, in the official pages we read, an activity log that attributes work to an agent the way some other vendors now document. Teams should ask, in their own projects, how they will tell a person's edit from an agent's before they let either MCP publish.

What DevContentOps Teams Should Confirm First

Treat this as backoffice access from a new front door, not as a chat novelty. An editor who can publish in the backoffice can publish through the Editor MCP, so if your workflow expects a draft and then a human approval, do not give the connecting account a publish permission you are not willing to have an agent exercise. Keep write confirmations on in the AI client until you have a reason to turn them off. Keep the Developer MCP off production until official docs say otherwise; it can change document types, templates and users, a different risk class from the Editor MCP even when both are hosted on the same Cloud project. And agree how you will audit the work. If you cannot tell who or what changed a page, you are not ready to let the tools publish.