Umami MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UMAMI_URL | No | Base URL for the Umami API. Defaults to https://api.umami.is in Cloud mode. Required for self-hosted instances. | |
| UMAMI_API_KEY | No | API key from Umami Cloud dashboard (Required for Cloud mode). | |
| UMAMI_PASSWORD | No | Login password (Required for self-hosted mode). | |
| UMAMI_USERNAME | No | Login username (Required for self-hosted mode). | |
| UMAMI_USER_AGENT | No | Custom User-Agent for outbound requests (default: umami-mcp/1.0). | umami-mcp/1.0 |
| UMAMI_CF_ACCESS_CLIENT_ID | No | Cloudflare Access service token client ID (for protected self-hosted APIs). | |
| UMAMI_CF_ACCESS_CLIENT_SECRET | No | Cloudflare Access service token secret. |
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 |
|---|---|
| get_websitesC | List all tracked websites in your Umami account. |
| get_statsB | Get summary statistics (pageviews, visitors, visits, bounces, totaltime) for a website over a date range. Timestamps are Unix milliseconds. |
| get_pageviewsC | Get time-series pageview and session data for a website, bucketed by the chosen time unit. |
| get_metricsC | Get a breakdown of metrics by a given dimension (url, referrer, browser, os, device, country, event, etc.) for a website. |
| get_activeB | Get the number of currently active visitors on a website (last 5 minutes). |
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 5 tools
Each tool has a clearly distinct purpose: get_active focuses on real-time visitor counts, get_metrics provides dimensional breakdowns, get_pageviews offers time-series data, get_stats gives summary statistics, and get_websites lists available websites. There is no overlap or ambiguity in their functions.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix (e.g., get_active, get_metrics, get_pageviews, get_stats, get_websites). This uniformity makes the set predictable and easy to understand.
With 5 tools, this server is well-scoped for analytics purposes, covering key aspects like real-time data, metrics, time-series, summaries, and website listing. Each tool earns its place without feeling excessive or insufficient.
The toolset provides strong coverage for querying analytics data, including active visitors, detailed metrics, pageviews, stats, and websites. A minor gap is the lack of tools for configuration or management (e.g., adding websites or events), but agents can effectively work with the provided read-only operations.