# @mikusnuz/umami-mcp

MCP server for the Umami Analytics v3 API

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.0.1
- **Author:** mikusnuz
- **License:** MIT
- **npm:** @mikusnuz/umami-mcp
- **Source:** https://github.com/mikusnuz/umami-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-13T23:16:22.770Z
- **Version scanned:** 2.0.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get_me` — Get the currently authenticated user's profile information
- `get_my_websites` — Get the list of websites belonging to the current user
- `get_my_teams` — Get the list of teams the current user belongs to
- `update_my_password` — Update the current user's password (self-hosted Umami only; Cloud API keys cannot call this route)
- `verify_auth` — Verify the current authentication token is valid
- `get_share` — Resolve a public Umami share by its slug without authentication
- `heartbeat` — Check if the Umami server is running and healthy
- `complete_two_factor_login` — Complete a pending self-hosted Umami login after a tool reports that 2FA is required
- `send_event` — Send a custom event or pageview to Umami (useful for server-side tracking)
- `get_event_values` — Get event or session property values for a website
- `get_event_data_events` — Get event data events (custom event names and counts) for a website
- `get_event_data_fields` — Get event data fields (property keys and their data types) for a website
- `get_event_data_properties` — Get custom-event property names and their data types for a website
- `get_event_data_by_id` — Get the custom data attached to one event
- `get_event_data_values` — Get event data values (aggregated counts for a specific property) for a website
- `get_event_data_stats` — Get event data statistics (summary counts) for a website
- `batch_events` — Send multiple events or pageviews in a single batch request
- `send_identify` — Attach custom session data or a distinct ID through Umami's public collection API
- `send_performance` — Send Core Web Vitals through Umami's public collection API
- `get_realtime` — Get real-time data for a website (last 30 minutes). Returns current visitors, active URLs, referrers, countries, and events.
- `list_reports` — List saved reports for a website
- `get_report` — Get details of a specific saved report
- `create_report` — Create and save a new report
- `update_report` — Update an existing saved report
- `delete_report` — Delete a saved report
- `run_report` — Execute a current Umami v3 report and return its result
- `get_session` — Get details of a specific session
- `get_session_activity` — Get activity log for a specific session (pages visited, events fired)
- `get_session_properties` — Get custom properties attached to a specific session
- `get_session_data_properties` — Get session data property names and their data types for a website
- `get_session_data_values` — Get session data values (aggregated counts for session properties) for a website
- `get_stats` — Get summary statistics for a website (pageviews, visitors, visits, bounces, totaltime)
- `get_pageviews` — Get pageview and session counts over time for a website
- `get_metrics` — Get aggregated metrics for a website (e.g. top pages, browsers, countries, devices, OS, events)
- `get_events` — List event rows for a website with current Umami v3 filters and pagination
- `get_sessions` — Get session data for a website
- `get_daterange` — Get the date range of available data for a website
- `get_event_series` — Get event metrics over time (event series data) for a website
- `get_session_stats` — Get summarized session statistics for a website (total sessions, unique visitors, etc.)
- `get_sessions_weekly` — Get weekly session data for a website

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"umami\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mikusnuz/umami-mcp\"\n      ],\n      \"env\": {\n        \"UMAMI_PASSWORD\": \"<YOUR_UMAMI_PASSWORD>\",\n        \"UMAMI_API_KEY\": \"<YOUR_UMAMI_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `UMAMI_PASSWORD` — Umami Password (optional)
- `UMAMI_API_KEY` — Umami API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 54, ceiling 54 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mikusnuz%2Fumami-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40mikusnuz%2Fumami-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mikusnuz%2Fumami-mcp
- HTML page: https://forgeregistry.com/registry/%40mikusnuz%2Fumami-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.