@byterover/umami-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UMAMI_API_KEY | No | Umami Cloud API key for read-only access. | |
| UMAMI_API_URL | No | Umami API base URL. For Cloud default https://api.umami.is, for self-hosted required. | |
| UMAMI_API_PATH | No | API path prefix. Cloud uses /v1, self-hosted uses /api. | |
| UMAMI_PASSWORD | No | Password for self-hosted Umami login. | |
| UMAMI_USERNAME | No | Username for self-hosted Umami login. |
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 the websites (id, name, domain) visible to these credentials. Start here to get a websiteId. |
| data_rangeA | The earliest and latest timestamps with collected data for a website. Call this before querying ranges so you don't ask for windows that have no data. |
| website_statsA | Summary metrics for one website over a date range: pageviews, visitors, visits, bounces, total time (each with the prior-period value for comparison). |
| pageviews_seriesB | Time series of pageviews and sessions for a website over a date range, bucketed by unit. |
| realtimeA | Live activity for a website over the last ~30 minutes: active visitors, recent views and events. |
| metricsA | Top values for one dimension of a website's traffic over a date range — e.g. type=url for top pages, type=referrer for top referrers, type=browser / os / device / country / event. Set expanded=true for engagement detail (visitors, visits, bounce, duration per row). |
| events_seriesB | Time series of tracked custom events for a website over a date range, bucketed by unit. |
| explore_event_dataB | Drill into custom-event PROPERTIES (not just counts over time). Modes: events = event names + counts; properties = property names per event; fields = property/value counts; stats = totals; values = counts for one event+property (both required for this mode). |
| list_sessionsA | List individual visitor sessions for a website over a date range (paginated). Each session carries browser/OS/device, geo, and visit/view/event counts. Use it to answer per-visitor questions. |
| session_detailA | Everything about one session: its summary, its activity log (the pages/events in order), and its custom properties — fetched together. Get a sessionId from list_sessions first. |
| funnel_reportB | Conversion funnel: given an ordered list of steps (each a page path or an event), how many visitors reach each step and where they drop off. Minimum two steps. |
| retention_reportC | Retention: of the visitors first seen in the range, what fraction return on each subsequent day. Requires a timezone. |
| journey_reportC | User journeys: the common navigation paths between a starting step and an (optional) ending step, over a chosen number of steps (3–7). |
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 13 tools
Each tool targets a distinct area of Umami analytics (time series, events, sessions, reports, etc.) with clear boundaries. The few overlaps, like metrics vs website_stats, are differentiated by purpose (top values vs summary aggregates).
All tool names are lowercase snake_case, following a consistent pattern of verb_noun (e.g., list_websites, explore_event_data) or descriptive compound nouns (e.g., funnel_report, data_range). No mixing of styles or conventions.
13 tools is well-scoped for an analytics server, covering all major data categories (pageviews, events, sessions, reports, realtime, website info) without unnecessary bloat or too few options.
The tool set covers all core Umami functionalities: website listing, stats, time series for pageviews and events, session exploration, funnel/journey reports, retention, realtime, and data boundaries. No obvious gaps for a read-only analytics API.