v0.1.0
Umami Compass 0.1.0 — Initial public release
Umami Compass reaches its first public release: a secure, read-only Model Context Protocol server for Umami Analytics 3.2+, supporting both Umami Cloud and self-hosted deployments.
Note
This is a historical release. New installations should use the current stable version; exact-version instructions below are provided for reproducibility.
Highlights
- 30 read-only MCP tools across core analytics, events, sessions, Core Web Vitals, reports, revenue, replay metadata, and heatmaps.
- Least-privilege defaults with only the aggregate
coretoolset enabled initially. - Three authentication modes: Umami Cloud API key, self-hosted Bearer token, or cached username/password login.
- Decision support: funnels, goals, journeys, retention, attribution, UTM analysis, revenue, bounded heatmaps, and replay metadata.
- MCP-native integration: structured tool output, resources, guided prompts, runtime schemas, and read-only annotations.
Security and reliability
- Fixed-origin upstream networking and HTTPS enforcement.
- Optional website UUID allowlist.
- Bounded date ranges, pages, response sizes, and high-cardinality results.
- Request timeouts, cancellation propagation, generation-safe login refresh, and redacted upstream errors.
- No tool in this release changes Umami state.
Install
Current stable release:
npx --yes --prefer-online umami-compass@latestReproduce this exact version:
npx --yes umami-compass@0.1.0Requires Node.js 22 or newer. Restart the MCP process after changing versions.
Verification
- CI on Node.js 22, 24, and 26.
- 45 automated tests plus TypeScript build and packed-package MCP smoke testing.
- Published from commit
d59b92a.
Distribution
License: MIT.