Matomo-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATOMO_URL | Yes | Matomo instance URL (required). Must point at the Matomo root containing index.php. | |
| MATOMO_TOKEN | No | API token (token_auth); view access is enough. Not needed for the public demo at demo.matomo.cloud. | |
| MATOMO_INSECURE | No | Accept self-signed TLS certificates (explicit opt-in). | false |
| MATOMO_TIMEOUT_SECS | No | Per-request timeout in seconds. | 30 |
| MATOMO_EXTRA_HEADERS | No | Extra HTTP headers (e.g., 'Name:Value') for auth proxies, Zero-Trust, etc. Repeatable/comma-separated. | |
| MATOMO_DEFAULT_SITE_ID | No | Site ID used when the model doesn't specify one (e.g., '1'). | |
| MATOMO_MAX_RESPONSE_CHARS | No | Response budget before truncation. | 50000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| matomo_list_sitesA | List all websites in Matomo that this token can access, with their ID, name and main URL. Call this first whenever the site_id is unknown. |
| matomo_visits_summaryA | Key traffic metrics for a site and period: visits, unique visitors, actions (pageviews), bounce rate, actions per visit, and average visit duration. The go-to tool for 'how much traffic did we get?'. |
| matomo_pagesA | Page-level analytics: most visited page URLs or titles, entry and exit pages, file downloads, and clicked outbound links. URLs are returned flattened (full paths), sorted by visits. |
| matomo_referrersB | Where traffic comes from: channel overview (direct, search, websites, social, campaigns), referring websites, search engines and keywords, social networks, campaign performance, and AI assistants (Matomo 5.1+). |
| matomo_eventsA | Custom event tracking reports (clicks, video plays, form interactions, ...), grouped by event category, action, or name. |
| matomo_goalsA | Goal conversions: overall conversion counts, rates and revenue (report=conversions), or the list of configured goals with their IDs (report=list). |
| matomo_ecommerceA | E-commerce performance: revenue/order overview, and best-selling products by product name, SKU, or category. |
| matomo_geoA | Visitor locations: visits broken down by country, continent, region, or city. |
| matomo_devicesB | Devices and technology used by visitors: device types (desktop, mobile, tablet), brands, models, browsers, browser versions, operating systems, and screen resolutions. |
| matomo_visit_timesA | When visitors come to the site: traffic by day of week, or by hour of day (server time or the visitor's local time). |
| matomo_site_searchA | Internal site-search analytics: what visitors searched for on the site, searches that returned no results, and search categories. |
| matomo_realtimeA | Real-time analytics: live visitor/action/conversion counters for the last N minutes (report=counters), or a detailed log of the most recent individual visits (report=last_visits). |
| matomo_page_performanceB | Page load performance: average network, server, transfer, DOM processing and rendering times across pageviews. |
| matomo_annotationsA | Annotations placed on the Matomo timeline (deploy markers, campaign launches, notes) for a date range — correlate traffic changes with what happened when. Defaults to the last 30 days. |
| matomo_apiA | Escape hatch: call ANY Matomo Reporting API method directly. Prefer the dedicated matomo_* tools; use this for reports they don't cover (custom dimensions, funnels, heatmaps, segment management, ...). Discover available methods with method='API.getReportMetadata'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct analytics dimension—visits, pages, referrers, events, goals, ecommerce, geo, devices, time, search, realtime, annotations—with no overlapping purposes. The api escape hatch is clearly set apart as a fallback for uncovered reports, eliminating boundary ambiguity.
All tools follow a uniform 'matomo_<descriptor>' pattern using lowercase snake_case with consistent noun-phrase naming. Every tool clearly indicates its domain (e.g., matomo_site_search, matomo_page_performance) without any verb-style mixes or camelCase deviations.
15 tools is at the upper end but perfectly sized for a comprehensive analytics server covering the full spectrum of Matomo reports—from aggregate visits to realtime and annotations—plus an API escape hatch. Each tool serves a distinct, necessary purpose without redundancy.
The surface covers all major analytics dimensions (traffic, content, referrers, events, goals, ecommerce, geography, technology, time, search, realtime, annotations) and includes an API tool to handle any custom or niche reports. This constitutes a complete lifecycle for web analytics queries with no obvious dead ends.