umami-compass
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UMAMI_URL | No | Self-hosted Umami instance origin (e.g., https://analytics.example.com); /api is appended. | |
| UMAMI_API_KEY | No | Umami Cloud API key (x-umami-api-key). | |
| UMAMI_API_URL | No | Exact API root URL for self-hosted Umami (alternative to UMAMI_URL). | |
| UMAMI_PASSWORD | No | Password for self-hosted Umami login (used with UMAMI_USERNAME). | |
| UMAMI_TOOLSETS | No | Comma-separated toolsets or 'all'. Defaults to 'core'. | |
| UMAMI_USERNAME | No | Username for self-hosted Umami login (used with UMAMI_PASSWORD). | |
| UMAMI_WEBSITE_IDS | No | Comma-separated website UUID allowlist. | |
| UMAMI_ACCESS_TOKEN | No | Existing Bearer token for self-hosted Umami. | |
| UMAMI_MAX_RANGE_DAYS | No | Max analytics range in days (1-3650). Defaults to 366. | |
| UMAMI_MAX_RESPONSE_BYTES | No | Max decoded upstream JSON body bytes (102400-52428800). Defaults to 10485760. | |
| UMAMI_REQUEST_TIMEOUT_MS | No | Per-request timeout in ms (1000-120000). Defaults to 30000. | |
| UMAMI_ALLOW_INSECURE_HTTP | No | Allow non-loopback HTTP connections. Defaults to 'false'. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_infoA | Get the local package version, enabled toolsets, safety limits, and supported analysis capabilities without exposing credentials. |
| list_websitesA | List websites visible directly or through any team membership of the configured Umami identity. If UMAMI_WEBSITE_IDS is set, returns only that exact allowlist. |
| get_websiteB | Get metadata for one website. |
| get_website_statsB | Get visits, visitors, pageviews, bounces, visit duration and Umami's comparison values for a time range. |
| get_pageviewsB | Get Umami 3.2 pageview and session time series. Both arrays are preserved in the response. |
| get_metricsA | Get a ranked aggregate Umami metric breakdown such as paths, referrers, countries, devices, events, channels or URLs. Visitor identifiers are excluded from the core toolset. |
| get_active_visitorsA | Get the current number of active visitors for a website. |
| get_website_date_rangeA | Get the earliest and latest analytics timestamps available for a website. |
| resolve_websiteA | Resolve a website UUID from a UUID, domain, URL, or website name. Ambiguous matches return bounded candidates instead of guessing. |
| get_portfolio_overviewB | Summarize bounded aggregate traffic across visible websites, including period changes, growth and decline leaders, stale tracking, failures, and suspicious jumps. |
| explain_traffic_changeA | Compare traffic with a previous, year-over-year, or custom period and rank observed changes across pages, referrers, countries, devices, channels, and events. Results describe association, not causation. |
| compare_traffic_seriesA | Return aligned current and comparison traffic buckets to locate the exact day or hour when traffic changed. |
| analyze_release_impactA | Compare equal pre- and post-release windows across traffic breakdowns and Core Web Vitals. Returns a compact executive summary by default; request full detail for drill-down evidence. Recent releases use a partial post window and an equally shortened pre window. |
| tracking_health_checkA | Audit visible websites for stale or missing traffic, traffic drops, domain mismatches, referral-spam patterns, custom-event availability, recorder configuration, and section permission failures. Disabled optional features are warnings only when marked as expected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analytics_report | A safe workflow for producing an evidence-based analytics report. |
| weekly_portfolio_briefing | Produce a bounded weekly briefing across visible websites with leaders, declines, anomalies, stale tracking, and next actions. |
| investigate_traffic_change | Explain a website traffic increase or decrease with bounded supporting evidence. |
| release_impact_report | Assess traffic and Web Vitals before and after a deployment. |
| tracking_health_audit | Check freshness, domains, events, recorder configuration, and permissions across websites. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| websites | Websites visible under the configured identity and optional allowlist. |
| capabilities | Sanitized local capability, scope, and safety-limit information without credentials. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/webcredo/umami-compass'
If you have feedback or need assistance with the MCP directory API, please join our Discord server