Log inSubmit server
Umami MCP logo

Umami MCP

by mikusnuz

Connects MCP-compatible AI clients to Umami Analytics for website administration, analytics, event collection, reports, and realtime data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Umami MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mikusnuz-umami-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/umami-mcp"
      ],
      "env": {
        "UMAMI_MODE": "YOUR_VALUE_HERE",
        "UMAMI_URL": "YOUR_VALUE_HERE",
        "UMAMI_USERNAME": "YOUR_VALUE_HERE",
        "UMAMI_PASSWORD": "YOUR_VALUE_HERE",
        "UMAMI_API_KEY": "YOUR_VALUE_HERE",
        "UMAMI_COLLECTOR_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

mikusnuz/umami-mcp connects MCP clients to Umami Analytics v3 through self-hosted or Cloud deployments. It exposes tools for website management, statistics, sessions, events, reports, boards, segments, replay, revenue, teams, and realtime monitoring. Authentication supports self-hosted credentials, self-hosted API keys, and Umami Cloud API keys, while public collection routes can send events without credentials. Reach for it when an agent needs to inspect or manage Umami data, submit server-side analytics, or work with supported Umami administration features.

Use cases

  • Inspect website traffic and visitor trends
  • Manage tracked websites and ownership
  • Send server-side events and pageviews
  • Run saved analytics and attribution reports
  • Monitor active visitors and realtime data

Key features

  • Umami v3 Cloud and self-hosted support
  • Website administration and ownership transfer
  • Analytics, sessions, events, and metrics queries
  • Event, pageview, performance, and batch collection
  • Reports, boards, segments, replay, and revenue tools
  • Realtime monitoring and team administration

Tools66

What Umami MCP lets your agent do. Expand a tool for its parameters.

Verified live~6.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

17/18 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @mikusnuz/umami-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8Stargazers on the source repository.
npm downloads282Package downloads in the last 30 days.
Last commit9d agoMost recent push to the default branch.
Tools exposed66Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Umami MCP works

What mikusnuz/umami-mcp does

mikusnuz/umami-mcp exposes the documented Umami Analytics v3 API through the Model Context Protocol. It covers analytics queries, website administration, event collection, reports, boards, links, pixels, segments, annotations, session replay, shares, exports, performance data, revenue, users, teams, two-factor authentication flows, and realtime information.

The server supports Umami instances compatible with v3.3 and newer, with API-key features requiring Umami 3.4 or later. It can also connect to Umami Cloud when the relevant routes are available. Use MCP tools/list to inspect the complete tool inventory and input schemas.

How it works

Management and analytics requests use a bearer token. With self-hosted username and password authentication, the server logs in only when needed and caches the resulting JWT. API keys are passed directly as bearer credentials. Public collection and selected public routes do not require authentication.

Self-hosted requests use the configured Umami instance URL. Cloud requests default to the Umami Cloud API and translate self-hosted-style paths to Cloud paths. A separate collector URL can be configured for public collection, sharing, heartbeat, and recorder endpoints.

The server handles Umami-specific API contracts, including raw-array batch requests, the v3 event shape for pageviews, path-based URL metrics, and timezone requirements for selected time-series tools. Batch collection accepts up to 500 items and reports processing results, errors, and per-item details.

Setup and configuration

Use Node.js 20 or newer. Install the package globally with npm install -g @mikusnuz/umami-mcp, or launch it with npx -y @mikusnuz/umami-mcp from an MCP client's stdio configuration.

For self-hosted Umami, set UMAMI_URL and either UMAMI_USERNAME plus UMAMI_PASSWORD, or UMAMI_API_KEY on Umami 3.4 and later. UMAMI_MODE=self-hosted can explicitly select that deployment type. For Umami Cloud, provide UMAMI_API_KEY; UMAMI_URL is optional unless a specific region or proxy is needed. Set UMAMI_MODE=cloud for a Cloud proxy on another hostname.

UMAMI_COLLECTOR_URL optionally selects a separate host for public collection and related routes. Cloud defaults this collector to https://cloud.umami.is; self-hosted deployments default to UMAMI_URL.

Tools and capabilities

  • List, create, update, delete, reset, and transfer websites.
  • Query statistics, pageviews, metrics, events, sessions, event series, session properties, and date ranges.
  • Inspect individual session details, activity, and custom properties.
  • Send events and pageviews, identify visitors, send performance data, and submit raw event batches.
  • Manage and execute reports, including attribution, funnel, goal, heatmap, journey, retention, revenue, and UTM report types.
  • Work with boards, links, pixels, segments, cohorts, annotations, shares, exports, replay data, and revenue analytics.
  • Manage supported users, teams, two-factor authentication flows, and realtime data.

Limitations and notes

Umami Cloud API keys do not expose the /me/password, /users, or /users/* routes; those user tools apply to self-hosted instances. Annotation writes require Umami 3.4 or later and website edit permission. Event series and weekly session queries require an IANA timezone. Team website membership changes use transfer_website, and removed team-website routes are not exposed.

The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Umami MCP

mikusnuz/umami-mcp is an MCP server that connects AI clients to Umami Analytics v3. Its main tools manage websites, query statistics, sessions, events, reports, and realtime data, while also supporting event collection, administration, Cloud API keys, and self-hosted username/password or API-key authentication.

Install it with `npm install -g @mikusnuz/umami-mcp` or run it directly with `npx -y @mikusnuz/umami-mcp`. Configure the command in an MCP client using stdio, then provide the Umami connection variables for a self-hosted instance or Cloud.

Use `UMAMI_URL` with `UMAMI_USERNAME` and `UMAMI_PASSWORD` for self-hosted login, or use `UMAMI_API_KEY` for Umami Cloud and self-hosted Umami 3.4 or newer. Set `UMAMI_MODE` when explicit deployment selection is needed.

Yes, it can send events and pageviews, submit identify and performance data, and send raw batches of up to 500 items. These public collection routes do not require credentials, and batch requests use Umami's raw JSON array format.

Yes, it uses the standard MCP stdio transport and can be configured in Cursor as an MCP server. Add the package command and the appropriate Umami environment variables to Cursor's MCP configuration.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUmami MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mikusnuz-umami-mcp?style=directory)](https://allmcps.com/mcp/mikusnuz-umami-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mikusnuz-umami-mcp"><img src="https://allmcps.com/api/badge/mikusnuz-umami-mcp?style=directory" alt="Umami MCP on AllMCPs" /></a>