matomo-mcp-client

An MCP (Model Context Protocol) server that acts as a client to the Matomo Analytics API. It exposes Matomo analytics data as MCP tools, allowing any MCP-compatible LLM client (Claude Desktop, Claude Code, etc.) to query your Matomo instance using natural language.

In other words: it's an MCP server (tools over stdio) and a Matomo API client (HTTP requests) in one.

• Direct connection to your Matomo instance, no remote proxy
• 16 analytics tools: traffic, pages, search, performance, and traffic sources
• Docker ready or run with Node.js
• Credentials stay local, never sent to third parties
• Retry logic with exponential backoff and timeout handling
• Supports self-signed certificates (common for internal servers)

git clone https://github.com/lucaspretti/matomo-mcp-client
cd matomo-mcp-client
docker build -t matomo-mcp-server .
cp .env.example .env
# Edit .env with your Matomo URL and API token

git clone https://github.com/lucaspretti/matomo-mcp-client
cd matomo-mcp-client
npm install

Copy .env.example to .env and fill in your values:

| Variable | Required | Description | |---|---|---| | MATOMO_HOST | Yes | Your Matomo instance URL | | MATOMO_TOKEN_AUTH | Yes | Matomo API token (Settings > Personal > Security > Auth Tokens) | | MATOMO_DEFAULT_SITE_ID | No | Default site ID (default: 1) | | REQUEST_TIMEOUT | No | Request timeout in ms (default: 30000) | | RETRY_COUNT | No | Retry attempts (default: 3) | | RETRY_DELAY | No | Initial retry delay in ms (default: 1000) |

Add to your MCP client configuration (e.g., claude_desktop_config.json):

{
  "mcpServers": {
    "matomo": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "--env-file", "/absolute/path/to/.env",
        "matomo-mcp-server"
      ]
    }