Umami MCP Server

Umami MCP server exists for a simple reason — assistants are far more useful when they can act on Umami directly instead of describing what you should do. Connect your Umami Analytics to any MCP client - Claude Desktop, VS Code, Cursor, Windsurf, Zed, Smithery, and more.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Umami is connected, these are the calls the assistant has available:

• get_websites — List all websites (call this first to get website IDs)
• get_stats — Aggregated statistics — pageviews, visitors, bounces, total time
• get_pageviews — Pageview and session counts grouped by time unit
• get_metrics — Breakdown by page, referrer, browser, OS, device, country, etc
• get_active — Current active visitor count in real-time
• get_sessions — List individual visitor sessions, with total count — the sessions session replay records
• get_session_stats — Aggregated session totals — pageviews, visitors, visits, countries, events
• get_session_activity — Ordered pageview/event timeline for a single session
• Local — Run the binary or Docker image locally. Credentials are set via environment variables

Configuration and credentials

You will need 5 environment variables: UMAMI_URL, UMAMI_USERNAME, UMAMI_PASSWORD, UMAMI_API_KEY, UMAMI_TEAM_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Umami.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the umami mcp server does with a few real requests.

Choosing this one

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Umami's toolset — get_websites, get_stats, get_pageviews and 6 more — is a fair guide to whether it matches your workflow. It is maintained by Macawls; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.