Sign up for Winter Keynote, Feb 2, 16:30 CET

Save the date →

Umbraco CMS Editor MCP and Developer MCP are now live on Umbraco Cloud!

Connect your AI client to your Umbraco project and work directly from the chat

Bolette Kern
Written by Bolette Kern

AI is no longer just inside the Umbraco backoffice, it works from the outside in. Whether in daily AI clients or developer tools like Cursor, VS Code, and Claude Code, external tools can now seamlessly connect directly to your CMS. Today, we're thrilled to make that a whole lot easier for you, your editor, developer, or client: 

CMS Editor MCP and CMS Developer MCP are officially live as remote MCPs, hosted on Umbraco Cloud! In short, you can now install the package on your Umbraco Cloud project once, and each project gets its own secure connection. After that, anyone on your team can connect ChatGPT, Claude.ai, or another AI client directly to your project's backoffice and find, create, and update content from the chat.

Let's find out how exactly: 

In ChatGPT, create a custom MCP app, give it a name, and provide the URL to your Umbraco Cloud project. Connect. Authorise against Umbraco Cloud. In the chat, choose your newly created Umbraco CMS MCP and start creating or editing content inside your project.

What's new, and why we're excited

Until now, using an Umbraco MCP meant running it on your own machine: installed with npx, a config file, and an API user. That's great for developers. But your editors don't run npx, and they shouldn't have to.

With remote MCPs on Umbraco Cloud, the connection runs cloud to cloud. Your AI client talks directly to your Umbraco Cloud project.

  • CMS Editor MCP is for editors and marketers, in the AI client they already like. It has a focused set of tools for content, media, translations, and members, and it stays out of the Settings section: it can't change document types, data types, or templates, and it can't manage users.

  • CMS Developer MCP is the Umbraco MCP developers already use, now hosted, for their coding tool or AI agent. It covers nearly everything in the backoffice, including Settings and Users.

For editors and marketers: Umbraco becomes one more connector

With CMS Editor MCP, Umbraco shows up next to the other connectors in your AI client, like Google Drive, Slack, or your email. In one conversation, you can pull in a brief from Drive or a thread from Slack, and turn it into content in your Cloud project.

 Umbraco as one more connector in the editor's AI client, next to Google Drive and Slack.
Diagram linking Google Drive, Slack, and email to an AI client, with Umbraco Cloud project text and links.
Editors connect the AI client they already use to your Umbraco Cloud project, right next to connectors like Google Drive and Slack. The CMS Editor MCP signs in as the editor, so their own backoffice permissions decide what the AI can find, update, create, and publish.

What you can do includes:

  • Content: find, create, edit, publish, and organise pages, including block editors and drafts
  • Media: upload, organise and move media
  • Translation: create language variants and spot missing translations
  • Content health: find stale or thin content, run SEO checks, see what links to a page before you delete it

You stay in control

The AI client signs in as you, with your Umbraco Cloud login. That means your own backoffice permissions decide what the AI can do. If you can't access a section in the backoffice, the AI can't either. There's no tool list to configure.

Write actions are designed to be confirmed before they run. Most AI clients ask for your approval before making a change, but this depends on your client, so check its settings if you want every change confirmed.

For developers: the MCP you know, without the local setup

CMS Developer MCP gives AI agents broad access to the Umbraco Management API: document types, data types, content, media, and much more. It's ideal for prototyping, debugging, and repetitive setup work.

The local version via npx isn't going anywhere. Now you can also connect your coding tool or AI agent to the hosted version on Umbraco Cloud, without installing or maintaining anything on your machine.

Part of MCP as a platform

Both MCPs are built on the same foundation, the Umbraco Base MCP SDK, which sits on top of the Umbraco Management API. It's the same foundation behind our Forms, Engage and Automate MCPs, and behind create-umbraco-mcp-server, which lets you build an MCP for your own package. This is what we mean by an agent-ready CMS: the plumbing is there, so you don't have to build it yourself.

Get started

Getting started on Umbraco Cloud has two parts: a one-time setup of your project, then connecting your AI client.

One-time setup (usually done by a developer)

  • Add the Umbraco.Mcp.HostedAuth package to your Cloud project: dotnet add package Umbraco.Mcp.HostedAuth
  • Deploy. That's it, no configuration needed. Umbraco Cloud already runs the hosted MCP for you.

Connect your AI client (anyone on the team)

  • Add Umbraco to your AI client: as a connector in Claude.ai, a plugin in ChatGPT, or in Claude Desktop, Cursor or VS Code.
  • Paste in your project's MCP URL. It looks like https://cms.editor.18.mcp.umbraco.ai/at/my-project.euwest01/mcp, with your own project alias, region and Umbraco version. Use developer instead of editor for the Developer MCP.
  • Log in with your Umbraco account and approve the connection.
  • Start asking, and have fun with it!

CMS Editor MCP is free on all Umbraco Cloud plans. Not on Umbraco Cloud? You can also host it yourself; see the self-hosted quickstart.

What comes next

Today, the CMS Editor MCP works from where you are in the content tree, so it handles pages that sit together, a batch at a time. Next on our public roadmap is Global Actions: the Editor MCP will search the whole site first, find exactly the content that matches your request, wherever it sits, and then work through it one item at a time.

That opens up requests like "find every blog post we haven't touched in 12 months, summarise each one, and tell me which to refresh, merge or retire." What would take an editor an afternoon of clicking through the tree becomes one request.

You stay in control here too: the AI still signs in as you, so it can't do more than you could.

More MCPs on Umbraco Cloud. In Q1 2027, we plan to host the Forms, Engage and Automate MCPs on Umbraco Cloud too. They're already in public beta on npm for local use. Once hosted, editors and marketers can build forms, segments, and automations straight from their AI client, with no local setup.

Thank you, and tell us what you think

A huge thank you to everyone who tried the public beta and shared feedback along the way. You helped shape what ships today. Now we can't wait to hear how you and your editors use it, and what you'd like it to do next. Share your feedback on GitHub.