Provides access to Matomo's Reporting API to retrieve website analytics, including traffic and engagement summaries, referrer breakdowns, page performance metrics, and goal conversions with revenue data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Matomo MCP Show me last month's top pages by page views"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Read website acquisition, content, conversion, and engagement analytics from Matomo's Reporting API.
Part of Pipeworx — an MCP gateway connecting AI agents to 1573+ live data sources.
matomo_visit_summary — aggregate traffic and engagement
matomo_referrer_breakdown — acquisition channels and sources
matomo_page_performance — page views, entrances, exits, and time
matomo_goal_performance — conversions and revenue by goal
Related MCP server: Matomo MCP Server
Pass your Matomo installation URL as _baseUrl and a read-only auth token as _apiKey. Requests require HTTPS and send the token in a POST body. The pack is read-only.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"matomo": {
"url": "https://gateway.pipeworx.io/matomo/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/matomo/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1573+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"matomo": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-matomo"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-matomoIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Matomo data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Read-only website analytics, AI referrals, crawlers, goals, revenue, and funnels.
Query site stats, realtime visitors, breakdowns and goals from Plausible Analytics.
Read-only access to your Nexly web analytics: traffic, pages, acquisition, events, and reports.
Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.
