If you manage an Umbraco site, you've probably wished you could just ask someone to "add a new page under Products" or "find every article missing alt text" and have it done. That's the idea behind the Umbraco Editor MCP: it connects an AI assistant directly to your Umbraco backoffice, so editorial and content-management tasks can be carried out through a conversation instead of a series of manual clicks.
This isn't a replacement for the backoffice, and it isn't magic. It's a structured set of tools that map onto the same actions an editor already performs — creating pages, publishing, organising media, checking SEO — just accessible through natural language. Here's a gentle tour of what's on offer.
Content pages
The largest group of tools handles the everyday work of managing pages: searching the site tree, reading a page's current fields, creating and editing content, and publishing, unpublishing, scheduling, or moving it. There are also bulk versions of these for making the same change across several pages at once, plus tools for duplicating pages, rolling back to a previous version, and comparing a draft against what's currently live.
Media and the Library
Alongside pages, there are tools for browsing and searching the media library, uploading files, organising folders, and editing details like alt text. Reusable content items in the Library section (used for things like authors and categories) have their own equivalent set of tools.
Structured content and languages
Many Umbraco pages are built from blocks — rows of rich text, images, or other components. There's a dedicated set of tools for inspecting, adding, and editing these blocks without needing to rebuild the whole page structure by hand. For multilingual sites, other tools handle adding languages, creating translations, and finding pages that are missing a particular language variant.
Reporting and site health
A smaller set of tools looks at the site as a whole: auditing a page's SEO fields, summarising the structure of the content tree, finding orphaned or deeply nested pages, and reporting on things like broken references or member activity.
None of this replaces editorial judgement — an assistant using these tools still has to be told what to do, and destructive actions (deleting, publishing, bulk changes) are the kind of thing worth reviewing before they happen. But for the routine parts of content management, it's a useful shortcut worth knowing about.