@rampstack/umami-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UMAMI_API_KEY | Yes | Umami Cloud API key. | |
| UMAMI_API_BASE | No | Override for a regional base, e.g. .../v1/eu. | https://api.umami.is/v1 |
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 |
|---|---|
| list_websitesA | List every website on the Umami account: id, name, and domain. Call this first to discover valid website_id values for the other tools. |
| get_statsA | Summary stats for a website over a window: visitors, visits, pageviews, bounces, totaltime, plus the previous period's values and computed deltas. |
| get_pageviewsA | Pageviews and sessions as a timeseries over a window, bucketed by day or hour. |
| get_metricsA | Top values for one dimension over a window (e.g. top URLs, referrers, browsers). Returns [{ x: value, y: visitors }]. |
| get_event_dataA | Custom event-data properties collected over a window, optionally for one event name. Requires an Umami plan that exposes the event-data endpoints; returns a clear note if unavailable. For simple event counts use get_metrics with type=event. |
| cohort_reportC | One-call snapshot for a website: stats (with deltas) plus top 10 URLs, top 10 referrers, and top 10 events, over a range. |
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
Each tool has a clearly distinct purpose: listing websites, summary stats, pageview timeseries, top dimension values, custom event data, and a combined cohort report. Overlap is minimal and descriptions clarify boundaries.
Most tools follow the 'verb_noun' pattern (list_websites, get_stats, get_pageviews, get_metrics, get_event_data), but 'cohort_report' breaks the pattern with a noun_noun format, causing a minor inconsistency.
With 6 tools, the server is well-scoped for an analytics API. Each tool serves a distinct analysis need without redundancy or bloat.
The tool set covers all core analytics queries: listing websites, aggregate stats, timeseries pageviews, top metrics, event data, and a combined snapshot. No obvious gaps for read-only analytics.