ObsidianCorps Umami Analytics MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add umami-mcp -- npx -y @obsidiancorps/umami-mcp

{
  "mcpServers": {
    "umami-mcp": {
      "args": [
        "-y",
        "@obsidiancorps/umami-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.umami-mcp]
command = "npx"
args = ["-y", "@obsidiancorps/umami-mcp"]

{
  "mcpServers": {
    "umami-mcp": {
      "args": [
        "-y",
        "@obsidiancorps/umami-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "umami-mcp": {
      "args": [
        "-y",
        "@obsidiancorps/umami-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: 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.). The author declared them in the registry entry; get the values from the project itself.