Matomo Analytics MCP Server

Curated read-only Matomo Analytics tools: traffic, pages, referrers, e-commerce, real-time & more. The matomo analytics mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Claude ▸ Yesterday you had 14,472 visits (11,416 unique visitors, 66% bounce rate). Top acquisition channels: 1. Organic search — 6,120 visits (Google 92%) 2. Direct — 4,890 visits 3. AI assistants — 1,204 visits (↑ 31% vs. last week) Want me to break down which landing pages converted best? ```

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• matomo_list_sites — "Which sites do we track?"
• matomo_visits_summary — "How much traffic did we get last week?"
• matomo_pages — "What are our top pages? Where do people exit?"
• matomo_referrers — "Where do visitors come from? Which campaigns work? What do AI assistants send us?"
• matomo_events — "How often was the configurator opened?"
• matomo_goals — "What's our conversion rate per goal?"
• matomo_ecommerce — "Revenue this month? Best-selling products?"
• matomo_geo — "Which countries/cities do visitors come from?"
• matomo_devices — "Mobile vs. desktop? Which browsers?"
• matomo_visit_times — "When during the day/week do people visit?"
• matomo_site_search — "What do people search for on our site — and find nothing?"
• matomo_realtime — "Who's on the site right now?"

Configuration

You will need 4 environment variables: MATOMO_URL, MATOMO_TOKEN, MATOMO_DEFAULT_SITE_ID, YOUR_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Matomo Analytics.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the matomo analytics mcp server does with a few real requests.

When to reach for it

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Matomo Analytics's toolset — matomo_list_sites, matomo_visits_summary, matomo_pages and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Liohtml; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Matomo Analytics's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.