Is Matomo agent-ready?

Matomo 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 Matomo publish an OpenAPI spec?

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

What is Matomo's Headless Index score?

Matomo scores 66/100 on the Headless Index thesis-fit rubric and sits in Band B 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

Matomo

Headless Index

66/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

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

Editorial verdict

Matomo is solidly built for programmatic consumption. The Headless Index thesis-fit score of 66/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 Matomo lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Matomo dispatches nearly every report through one RPC endpoint (index.php?module=API&method=VisitsSummary.get&format=json), which is unusual and, for an agent, workable: one shape, hundreds of methods. Tracking has separate first-party clients in PHP, Node, Java, iOS and Android (matomo-org/matomo-php-tracker). 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: Every configuration object has a method: SitesManager.addSite, UsersManager.addUser, Goals.addGoal, SegmentEditor.add. Core ships a real CLI (./console core:archive, plugin:activate), settings can be driven by environment variables (matomo-org/plugin-EnvironmentVariables), and the official Docker image is maintained in-house. What is missing is declarative state; there is no Terraform provider, so agents write imperative call sequences. Nothing in the admin UI is off limits to the API, which is rare in this category.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Matomo ships a first-party MCP server as a core-org plugin (matomo-org/plugin-McpServer), authenticating by OAuth2 client or a token_auth bearer, with optional write access that lets an agent create and update segments. There is an in-product connect guide under Administration, Platform, MCP Server. Because it is self-hosted, there is no registry endpoint to point a client at.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. This is the hole. Matomo core has no outbound webhook system at all, no event catalogue, no signing scheme, no retry semantics. The nearest thing is threshold alerting: matomo-org/plugin-CustomAlerts fires email (no HTTP callback anywhere), and matomo-org/plugin-Slack and plugin-MicrosoftTeams push those same alerts to chat. An agent that wants to react to traffic changes has to poll the Reporting API. Net assessment: Matomo 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 intent15/20

scored

Matomo dispatches nearly every report through one RPC endpoint (index.php?module=API&method=VisitsSummary.get&format=json), which is unusual and, for an agent, workable: one shape, hundreds of methods. Tracking has separate first-party clients in PHP, Node, Java, iOS and Android (matomo-org/matomo-php-tracker). The reporting clients are the weak half; piwik-dotnet-api has not been touched since 2017, and the Python and Ruby clients are close behind.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 0 probe paths
−GraphQL endpointNot discovered (0 probes; project-scoped endpoints require a real project ID)
+SDKs maintained6 (dotnet, java, python, ruby, swift); top by stars: matomo-org/matomo-sdk-android (425 stars)
+SDK recency1 of 6 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-03)

cite (1)

github.sdks@2026-08-19

Headless operation16/20

scored

Every configuration object has a method: SitesManager.addSite, UsersManager.addUser, Goals.addGoal, SegmentEditor.add. Core ships a real CLI (./console core:archive, plugin:activate), settings can be driven by environment variables (matomo-org/plugin-EnvironmentVariables), and the official Docker image is maintained in-house. What is missing is declarative state; there is no Terraform provider, so agents write imperative call sequences. Nothing in the admin UI is off limits to the API, which is rare in this category.

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

Matomo ships a first-party MCP server as a core-org plugin (matomo-org/plugin-McpServer), authenticating by OAuth2 client or a token_auth bearer, with optional write access that lets an agent create and update segments. There is an in-product connect guide under Administration, Platform, MCP Server. Because it is self-hosted, there is no registry endpoint to point a client at.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·MCP detector statusTimed out during collection (likely GitHub search API rate limit without GITHUB_TOKEN). No verified evidence about MCP presence.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Schema observability12/20

scored

No OpenAPI document exists and none is promised. What Matomo does have is introspection: API.getReportMetadata returns every report with its metrics and dimensions, API.getSegmentsMetadata returns the segment grammar, and a listAllAPI call enumerates the callable methods (module=API&action=listAllAPI). An agent can bootstrap from that, but it is a bespoke metadata format that no code generator reads. Cold client generation therefore still requires reading prose.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Collector statusOpenAPI and GraphQL probes did not record any attempts

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Webhooks & events6/20

scored

This is the hole. Matomo core has no outbound webhook system at all, no event catalogue, no signing scheme, no retry semantics. The nearest thing is threshold alerting: matomo-org/plugin-CustomAlerts fires email (no HTTP callback anywhere), and matomo-org/plugin-Slack and plugin-MicrosoftTeams push those same alerts to chat. An agent that wants to react to traffic changes has to poll the Reporting API.

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=66

04 / Embed

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

SegmentB

Headless Index 66/100

ClickHouseB

Headless Index 66/100

SnowplowB

Headless Index 64/100

See full Analytics & Events ranking →

FAQ

Matomo and agent readiness

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