Umami Analytics (Read-only)

io.github.MrLinWangPublished by GitHub account MrLinWangv0.1.0Updated Nov 19, 2026

Read-only Umami analytics for self-hosted sites: traffic, referrers, sessions and events.

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

Read-only MCP server that lets an assistant query traffic, referrers, sessions and events from a self-hosted Umami analytics instance.

What you can do
  • Query website traffic statistics from a self-hosted Umami instance
  • Inspect referrers, sessions and event data for tracked sites
  • Read analytics for one or more sites using a default website ID
  • Report on self-hosted site analytics without changing any data
When to use it
Useful when you run your own Umami instance and want an assistant to pull traffic, referrer, session or event numbers into a conversation or report without opening the dashboard.
Requirements
Runs locally over stdio from the npm package mrlinwang-umami-mcp (Node.js). Requires UMAMI_URL, the base URL of your self-hosted Umami instance, and UMAMI_API_TOKEN, an API key or login token with access to the sites you query. UMAMI_TIMEZONE (IANA name, defaults to UTC) and UMAMI_WEBSITE_ID are optional. Network access to the Umami instance is needed.
Before you install
Requires a Umami API key or login token in UMAMI_API_TOKEN, which grants access to the sites it covers; keep it out of shared logs and configs. The server is described as read-only, but the token's own permissions determine what is actually possible. Analytics data is sent from your instance to the assistant's model.

Installation

In SourceWeft

  1. Open Umami Analytics (Read-only) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.1.0LatestNov 19, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.