Is mParticle agent-ready?

mParticle 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 API-first design intent; its weakest is MCP and agent posture.

Does mParticle publish an OpenAPI spec?

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

What is mParticle's Headless Index score?

mParticle scores 57/100 on the Headless Index thesis-fit rubric and sits in Band C in the Analytics & Events category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Analytics & Events

mParticle

Headless Index

57/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

mParticle earns Band C in the Analytics & Events category of The Headless Index, with a thesis-fit score of 57/100. Its strongest dimension is API-first design intent (16/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when mParticle was scored, which limits how far an agent can go without human integration work.

Editorial verdict

mParticle is partially headless and partly UI-led. The Headless Index thesis-fit score of 57/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 mParticle lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Ingestion is the product and it shows. Events post to s2s.mparticle.com/v2/events under HTTP Basic key and secret, with regional hosts for eu1, au1 and us2, while api.mparticle.com carries Accounts, Apps, Audiences, Feeds, Services and Workspaces. 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: Data plans are the standout: schemas live in version control and ship through the Data Planning API and @mparticle/data-planning-node, which is closer to config-as-code than anything else in this category. Audiences have a typed package too (@mparticle/audience-sdk). Against that, no CLI binary ships, there is no Terraform provider, and wiring most of the several hundred output integrations still means the connection UI.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Absent. The org publishes dozens of SDKs (github.com/mParticle) and not one MCP server; the registry lists nothing, the developer docs carry no agent guidance, and what exists on GitHub is a single zero-traction third-party attempt. For a platform whose value is routing events between systems, having no tool interface for the systems now doing the routing is a conspicuous miss.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. MParticle forwards your events to hundreds of destinations, but it publishes almost nothing about events it sends you. Outbound goes through a generic webhook output integration or the partner Firehose contract (github.com/mParticle/mparticle-firehose-java-sdk), and DSR requests accept a status callback URL. There is no named event type list, no HMAC signing scheme, and no replay window an agent could rely on. Net assessment: integrators can build agent flows against mParticle, but the rough edge to plan around is MCP posture^[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 intent16/20

scored

Ingestion is the product and it shows. Events post to s2s.mparticle.com/v2/events under HTTP Basic key and secret, with regional hosts for eu1, au1 and us2, while api.mparticle.com carries Accounts, Apps, Audiences, Feeds, Services and Workspaces. Server SDKs are generated for Node, Python, Ruby, Go, Java and .NET (@mparticle/web-sdk runs roughly twenty thousand weekly installs). Several server clients have gone stale.

signals (6)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
·GraphQL endpointDiscovered at https://www.mparticle.com/graphql, introspection disabled or scoped
+SDKs maintained25 (dotnet, go, java, javascript, kotlin, python, ruby, swift, typescript); top by stars: mParticle/mparticle-android-sdk (68 stars)
+SDK recency4 of 25 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)
+npm weekly downloads23.9k across published packages; top: @mparticle/web-sdk @ 19.9k/week

cite (1)

github.sdks@2026-08-19

Headless operation14/20

scored

Data plans are the standout: schemas live in version control and ship through the Data Planning API and @mparticle/data-planning-node, which is closer to config-as-code than anything else in this category. Audiences have a typed package too (@mparticle/audience-sdk). Against that, no CLI binary ships, there is no Terraform provider, and wiring most of the several hundred output integrations still means the connection UI.

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

scored

Absent. The org publishes dozens of SDKs (github.com/mParticle) and not one MCP server; the registry lists nothing, the developer docs carry no agent guidance, and what exists on GitHub is a single zero-traction third-party attempt. For a platform whose value is routing events between systems, having no tool interface for the systems now doing the routing is a conspicuous miss.

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 SDKs6 TS/JS SDKs available; top: @mparticle/web-sdk (19.9k/week downloads)

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Schema observability13/20

scored

No OpenAPI document is published anywhere, which is odd given the server SDKs are plainly Swagger Codegen output. What mParticle does serve is JSON Schema for ingestion, live and fetchable (docs.mparticle.com/schema/mparticle.inbound.eventsapi.schema.json, plus a bulk variant). An agent can validate an event payload cold; it still cannot generate a Platform API client without reading the reference pages by hand.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://www.mparticle.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events10/20

scored

mParticle forwards your events to hundreds of destinations, but it publishes almost nothing about events it sends you. Outbound goes through a generic webhook output integration or the partner Firehose contract (github.com/mParticle/mparticle-firehose-java-sdk), and DSR requests accept a status callback URL. There is no named event type list, no HMAC signing scheme, and no replay window an agent could rely on.

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:C band: scores 40-75 range

04 / Embed

Show mParticle'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 Analytics & Events

TealiumC

Headless Index 58/100

PostHogC

Headless Index 58/100

MixpanelC

Headless Index 56/100

See full Analytics & Events ranking →

FAQ

mParticle and agent readiness

Is mParticle agent-ready?: mParticle 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 API-first design intent; its weakest is MCP and agent posture.
Does mParticle publish an OpenAPI spec?: No published OpenAPI specification was found when mParticle was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is mParticle's Headless Index score?: mParticle scores 57/100 on the Headless Index thesis-fit rubric and sits in Band C in the Analytics & Events category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.