Custom Umbraco MCP for Multi-Site Content Operations

How We Built a Custom Umbraco MCP to Run Our Marketing Sites Without Backend Logins

April 23, 2026

Eveliko built a custom Umbraco MCP that handles content authoring, preview, SEO and JSON-LD, navigation, content pipelines, and full-site onboarding from Claude, Cursor, and other MCP clients, with both OAuth and API Key authentication supported. Nearly 80 content pieces were produced on eveliko.com alone in ten weeks, and backend logins are now the exception rather than the routine across multiple Eveliko-operated sites.

MCP (Model Context Protocol) Claude Cursor GitHub Copilot AI Integrations

When Every Small Content Task Still Means a Backend Login

Backend logins are a tax on small, frequent content work.

Most marketing work is not large: publish a blog post, update a service page, refresh a hero section, fix metadata on one page. For an agency or a founder running multiple brands, the per-task login-to-publish overhead adds up to hours every week that produce nothing a reader ever sees.

Different tools require different MCP schemes.

Claude connects over OAuth. Cursor, CLI tools, and developer automations prefer API keys. A serious Umbraco MCP has to support both authentication paths as first-class options, or one audience is forced through the wrong mechanism and ends up building workarounds.

Campaigns go wrong in the same places every time.

A new case study is not a single page: it is a blog post, a listing entry, a navigation update, JSON-LD, and a preview link a stakeholder can actually click. Done by hand across a content tree, something always gets missed, usually the navigation or the schema, and it is only noticed after it has been live for a day.

Onboarding a new site should not take an afternoon.

Every new client or vertical brand needs the same Umbraco scaffolding: a root, templates, a navigation structure, correctly scoped content. Doing that by hand is mechanical work that should be a single tool call, not an afternoon.

A Custom Umbraco MCP That Runs the Full Content Lifecycle

An Umbraco MCP built around how content actually gets made.

Eveliko built a custom Umbraco MCP that exposes the full content lifecycle as MCP tools. Editors describe what they want in natural language from Claude, Cursor, or any compliant client, and the MCP creates pages, authors blog posts and case studies, manages navigation, runs content pipelines, and generates preview links, without the editor opening the Umbraco backend for the majority of tasks.

Both major authentication schemes supported: OAuth and API Key.

The MCP ships with OAuth and API Key authentication as Umbraco plugins. Claude connects over OAuth, which is the secure user-scoped path it expects; Cursor and developer automations use API keys. One MCP, both schemes, and no compromise between content operators and developers building tooling on top.

Content pipelines turn campaigns into a single reviewable unit.

Real content work is a campaign, not a page: a blog post, a landing page, a navigation entry, metadata updates, and a case study, all intended to ship together. The MCP stacks these into one reviewable pipeline, previewed as a whole and published atomically, so nothing goes live half-finished and navigation is never forgotten.

JSON-LD and SEO are first-class tools, not afterthoughts.

The MCP exposes dedicated tools for JSON-LD generation and SEO metadata updates. Organization, FAQPage, CollectionPage, BlogPosting, and Service schemas are updated alongside the content they describe, which is how eveliko.com's GEO score moved from the mid-40s into the mid-60s without any manual schema editing.

Site onboarding is one tool call.

Launching a new client, vertical, or brand site used to mean manual cloning, scope fixing, and navigation rewiring. The MCP exposes an onboarding tool that duplicates a template website, relates content correctly, and scopes it to the new tenant in a single operation, with consistent results every time.

The proof: over 100 content pieces in ten weeks.

Between February and April 2026, roughly 100 content pieces were produced on eveliko.com, accounting websites and the rest of the estates we operate in two languages. Mostly through this MCP: case studies, blog posts, service pages, and supporting content, more than the prior Eveliko marketing presence accumulated over several years. A Bulgarian accountant practice site and several other Eveliko-operated sites run the same way. Backend logins are the exception, not the routine. Our attitude towards content creation changed.