Is Drupal agent-ready?

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

Does Drupal publish an OpenAPI spec?

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

What is Drupal's Headless Index score?

Drupal scores 52/100 on the Headless Index thesis-fit rubric and sits in Band C 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

Drupal

Headless Index

52/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Drupal earns Band C in the Content Management category of The Headless Index, with a thesis-fit score of 52/100. Its strongest dimension is headless operation (14/20); its weakest scored dimension is webhooks and events (6/20). No public OpenAPI specification was found when Drupal was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Drupal is partially headless and partly UI-led. The Headless Index thesis-fit score of 52/100 puts it mid-table on 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 are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Drupal lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Drupal's API story is a module, not a product. JSON:API ships in core and is genuinely spec-compliant, with a self-describing resource index at /jsonapi; REST and the contrib GraphQL module (drupal.org/project/graphql) sit alongside it. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Config-as-code is a genuine strength here: every setting exports to YAML, Drush (drush/drush, over 60 million installs) drives install, config:import, cache rebuild and user creation, and Recipes package site setup for replay. The constraint for agents is transport. Drush is a server-side shell tool, not a remote control plane, so an agent without SSH is back to the browser.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: There is no vendor org to publish from, and it shows. Agent support lives in contrib: a Model Context Protocol module (drupal.org/project/mcp) and the wider AI initiative (drupal.org/project/ai), both installed per site rather than distributed as a hosted server. For a project this large, MCP remains an optional extension a site builder chooses to enable.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Nothing here is built in. Drupal has a rich internal event system in PHP, but no HTTP delivery, no catalogue of outbound event types, no signing scheme and no retry semantics. Sites bolt on contrib (drupal.org/project/webhooks) or wire dispatch rules through ECA. An agent that wants to react to a node publish has to build the notification path itself. Net assessment: integrators can build agent flows against Drupal, but the rough edge to plan around is webhooks and events^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

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 intent12/20

scored

Drupal's API story is a module, not a product. JSON:API ships in core and is genuinely spec-compliant, with a self-describing resource index at /jsonapi; REST and the contrib GraphQL module (drupal.org/project/graphql) sit alongside it. What does not exist is a single official client library in any language, so every integration starts by hand-rolling HTTP against a PHP monolith.

signals (4)

+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 maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation14/20

scored

Config-as-code is a genuine strength here: every setting exports to YAML, Drush (drush/drush, over 60 million installs) drives install, config:import, cache rebuild and user creation, and Recipes package site setup for replay. The constraint for agents is transport. Drush is a server-side shell tool, not a remote control plane, so an agent without SSH is back to the browser.

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)

github.sdks@2026-08-19

MCP & agent posture10/20

scored

There is no vendor org to publish from, and it shows. Agent support lives in contrib: a Model Context Protocol module (drupal.org/project/mcp) and the wider AI initiative (drupal.org/project/ai), both installed per site rather than distributed as a hosted server. For a project this large, MCP remains an optional extension a site builder chooses to enable.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

github.sdks@2026-08-19

Schema observability10/20

scored

Core ships no OpenAPI document. An agent can crawl the JSON:API index and infer resource types from it, which is better than nothing, but field-level types and required attributes are not described there. A formal spec requires installing contrib (drupal.org/project/openapi_jsonapi) on the site first, which means the schema is a deployment decision rather than a published artifact.

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)

github.sdks@2026-08-19

Webhooks & events6/20

scored

Nothing here is built in. Drupal has a rich internal event system in PHP, but no HTTP delivery, no catalogue of outbound event types, no signing scheme and no retry semantics. Sites bolt on contrib (drupal.org/project/webhooks) or wire dispatch rules through ECA. An agent that wants to react to a node publish has to build the notification path itself.

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)

github.sdks@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:C band: scores 40-75 range

04 / Embed

Show Drupal'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

Craft CMSC

Headless Index 52/100

PrismicC

Headless Index 53/100

StatamicC

Headless Index 50/100

See full Content Management ranking →

FAQ

Drupal and agent readiness

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