Matomo

Getting a token

1. Sign in to Matomo and open Administration → Personal → Security → Auth tokens, then Create new token.
2. Leave 'Only allow secure requests' unticked only if you must — with it ticked, Matomo 4+ requires the token in a POST body rather than a query parameter. This adapter sends it as a query parameter (GET), which is Matomo's classic Reporting API shape and what the majority of installs accept.
3. Set MATOMO_URL to your Matomo root (no trailing slash, no /index.php) and MATOMO_TOKEN to the token.

If every call returns an authentication error on Matomo 5, the token was created with the secure-requests flag. Create a second token without it, or build a custom connector that POSTs token_auth in the body.

Everything is one endpoint. Matomo's Reporting API is index.php?module=API&method=Module.action&idSite=…&period=…&date=…&format=JSON. That is why every tool here shares a path and differs only in the method parameter.

idSite, period and date are required on every report, and they mean:

• idSite — the numeric site id. matomo_list_sites gives you the list.
• period — day, week, month, year or range.
• date — 2026-09-17, or a keyword like today, yesterday, last7, last30, previous7. With period=range, a comma-separated pair: 2026-09-01,2026-09-30.

A multi-period request (period=day&date=last30) returns an object keyed by date, not a flat array. That is the shape, not an error.

Segments narrow a report without changing it: countryCode==de, deviceType==smartphone, visitCount>2, joined with ; for AND and , for OR.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (analytics.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.