Is Umbraco agent-ready?

Umbraco scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is webhooks and events.

Does Umbraco publish an OpenAPI spec?

No published OpenAPI specification was found when Umbraco was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Umbraco's Headless Index score?

Umbraco scores 63/100 on the Headless Index thesis-fit rubric and sits in Band B in the Content Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Content Management

Umbraco

Headless Index

63/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Umbraco earns Band B in the Content Management category of The Headless Index, with a thesis-fit score of 63/100. Its strongest dimension is MCP and agent posture (17/20); its weakest scored dimension is webhooks and events (8/20). No public OpenAPI specification was found when Umbraco was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Umbraco is solidly built for programmatic consumption. The Headless Index thesis-fit score of 63/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Umbraco lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Two REST surfaces exist and both are honestly designed: a read-oriented Delivery API, and a Management API that the v14 backoffice itself consumes, which means the admin UI cannot outrun the API. Client libraries are the gap. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Because the backoffice is a client of the Management API, document types, media, members and publishing all have programmatic equivalents. Production access is the problem: only the umbraco-back-office client is permitted there (OAuth2 authorization code with PKCE), with umbraco-swagger and umbraco-postman restricted to non-production. There is no first-party CLI beyond dotnet templates, and config-as-code is left to community uSync.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: This is the surprise of the category. Umbraco runs several MCP servers from its own org: a CMS server (github.com/umbraco/Umbraco-CMS-MCP-Dev) with commits this month, plus Forms and Commerce servers, and a base kit published as @umbraco-cms/mcp-server-sdk with a create-umbraco-mcp-server scaffold. Shipping a kit so others can build servers is a stronger posture than most larger vendors manage.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. The default catalogue is five entries wide (Content Published, Content Unpublished, Content Deleted, Media Saved, Media Deleted), filterable by document type, with payloads selectable as legacy, minimal or extended. Beyond that it thins out fast. Authentication is whatever custom header you configure, there is no signature over the body, and no retry or replay semantics are documented for a failed delivery. Net assessment: Umbraco can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent14/20

scored

Two REST surfaces exist and both are honestly designed: a read-oriented Delivery API, and a Management API that the v14 backoffice itself consumes, which means the admin UI cannot outrun the API. Client libraries are the gap. The published .NET client (github.com/umbraco/Umbraco.Headless.Client.Net) targets the older Heartcore service and has not been pushed since January 2025.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 0 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
·SDKs maintained2 (dotnet, typescript); top by stars: umbraco/Umbraco.Headless.Client.Net (13 stars)
−npm weekly downloadsNo published npm package detected for the JS/TS SDKs

cite (1)

github.sdks@2026-08-19

Headless operation12/20

scored

Because the backoffice is a client of the Management API, document types, media, members and publishing all have programmatic equivalents. Production access is the problem: only the umbraco-back-office client is permitted there (OAuth2 authorization code with PKCE), with umbraco-swagger and umbraco-postman restricted to non-production. There is no first-party CLI beyond dotnet templates, and config-as-code is left to community uSync.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture17/20

scored

This is the surprise of the category. Umbraco runs several MCP servers from its own org: a CMS server (github.com/umbraco/Umbraco-CMS-MCP-Dev) with commits this month, plus Forms and Commerce servers, and a base kit published as @umbraco-cms/mcp-server-sdk with a create-umbraco-mcp-server scaffold. Shipping a kit so others can build servers is a stronger posture than most larger vendors manage.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/umbraco/Umbraco.Commerce.Mcp (1 stars, last commit 7 days ago)
·Community MCP servers3 community MCP repos; top by stars: https://github.com/umbraco/Umbraco-CMS-MCP-Dev (39 stars)
+Agent-friendly SDKs1 TS/JS SDKs available; top: umbraco/Umbraco.Workflow.Client.Preview

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability12/20

scored

An OpenAPI document does exist, generated by the ASP.NET tooling (Microsoft.AspNetCore.OpenApi) and served with Swagger UI at {yourdomain}/umbraco/openapi, covering both Management and Delivery definitions. It is also disabled in production by design. An agent therefore cannot fetch a canonical schema from a vendor URL; it must stand up a development instance first, making cold client generation a build step.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 0 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Webhooks & events8/20

scored

The default catalogue is five entries wide (Content Published, Content Unpublished, Content Deleted, Media Saved, Media Deleted), filterable by document type, with payloads selectable as legacy, minimal or extended. Beyond that it thins out fast. Authentication is whatever custom header you configure, there is no signature over the body, and no retry or replay semantics are documented for a failed delivery.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:B band: JAIRF=N/A HeadlessIndex=63

04 / Embed

Show Umbraco's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Content Management

Agility CMSB

Headless Index 62/100

GhostB

Headless Index 60/100

DirectusC

Headless Index 59/100

See full Content Management ranking →

FAQ

Umbraco and agent readiness

Is Umbraco agent-ready?: Umbraco scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is webhooks and events.
Does Umbraco publish an OpenAPI spec?: No published OpenAPI specification was found when Umbraco was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Umbraco's Headless Index score?: Umbraco scores 63/100 on the Headless Index thesis-fit rubric and sits in Band B in the Content Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.