Matomo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATOMO_HOST | Yes | Base URL of your Matomo instance (e.g., https://analytics.yourcompany.com/). | |
| RETRY_COUNT | No | Maximum HTTP request retries. | 3 |
| RETRY_DELAY | No | Initial retry delay in ms. Multiplied exponentially on consecutive failures. | 1000 |
| REQUEST_TIMEOUT | No | HTTP request timeout in milliseconds. | 30000 |
| MATOMO_TOKEN_AUTH | Yes | Your Matomo secret API token (token_auth). | |
| MATOMO_DEFAULT_FORMAT | No | Default response format for reporting queries (e.g., json, xml). | json |
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_callB | Esegue qualsiasi metodo dell'HTTP Reporting API di Matomo (es. VisitsSummary.get, SitesManager.getSitesWithViewAccess). Parametri: method, params, format. |
| matomo_list_report_metadataB | Recupera lista completa di report compatibili da API.getReportMetadata. Utile per esplorazione. |
| matomo_get_metadataC | Recupera metadati per report specifico tramite API.getMetadata. Include schema, unità di misura, documenti. |
| matomo_get_processed_reportC | Recupera report completo processato con dati numerici tramite API.getProcessedReport. |
| matomo_get_row_evolutionC | Analizza evoluzione temporale di una singola riga di report tramite API.getRowEvolution. |
| matomo_get_image_graphC | Genera immagine PNG dello grafico tramite ImageGraph.get. |
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 6 tools
Tools have distinct purposes: generic API call, listing reports, getting metadata, processed reports, row evolution, and image graphs. However, matomo_call could be used to replicate the others, creating slight ambiguity.
All tools start with 'matomo_' followed by a verb phrase. Most use 'get' for retrieval, but 'list' and 'call' deviate slightly. Pattern is clear and mostly consistent.
6 tools is well-scoped for a Matomo analytics server. The set covers key interactions without being overwhelming, and the generic matomo_call fills any gaps.
Tools cover listing, metadata, processed data, row evolution, and graph generation. The generic matomo_call ensures any missing API method is accessible, making the surface complete.