ObsidianCorps Umami Analytics MCP Server

ObsidianCorps Umami Analytics is an MCP integration. Umami v3 MCP for Cloud or self-hosted analytics, with read-only, privacy-conscious defaults.

Packages and local setup

The published npm package is @obsidiancorps/umami-mcp, version 0.1.2. Its declared MCP transport is stdio.

The package declares UMAMI_API_KEY: Umami Cloud API key. Configure this or one self-hosted authentication mode.; UMAMI_BASE_URL: Base URL of a self-hosted Umami instance, for example https://analytics.example.com.; UMAMI_TOKEN: Pre-issued self-hosted Umami token. Use with UMAMI_BASE_URL instead of login credentials.; UMAMI_USERNAME: Self-hosted Umami username. Use with UMAMI_BASE_URL and UMAMI_PASSWORD.; UMAMI_PASSWORD: Self-hosted Umami password. Use with UMAMI_BASE_URL and UMAMI_USERNAME.; UMAMI_TWO_FACTOR_SECRET: Optional Base32 TOTP setup secret for automatic Umami 3.3+ two-factor login.; UMAMI_DEFAULT_WEBSITE_ID: Optional default website UUID used when a tool call does not select a website..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related analytics & reporting MCP servers for tools that cover the same kind of work.