@mitr-analytics/mcp

Ask Claude, Gemini or any other MCP client about your Mitr analytics, in plain English. It reads your own data (apps, reports, funnels, alerts, plan usage) and hands it to the assistant to analyse.

Mitr is cookie-free analytics, so there is no consent banner to wire up and nothing here changes that: this server only reads what is already in your dashboard.

What you can ask

• "Which of my apps had the biggest drop in visitors this week, and where did it come from?"

• "Show my signup funnel for the last 30 days. Where do people leave?"

• "Is anything odd in the last events for my marketing site? Are the UTM tags coming through?"

• "How much of my monthly event quota have I used?"

• "Register a new web app called Docs for docs.example.com."

Related MCP server: Clamp Analytics MCP Server

Set up (about two minutes)

You need Node.js 18 or newer, and a Mitr account.

1. Create an API key. In the dashboard open Settings → API keys & AI assistants → Create key, give it a name (for example "Claude Desktop") and copy it. It is shown once.

2. Add Mitr to your assistant.

Claude Desktop: open claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\) and add:

{
  "mcpServers": {
    "mitr": {
      "command": "npx",
      "args": ["-y", "@mitr-analytics/mcp"],
      "env": { "MITR_API_KEY": "mitr_live_..." }
    }
  }
}

Gemini CLI: add the same mcpServers block to ~/.gemini/settings.json.

Claude Code:

claude mcp add mitr --env MITR_API_KEY=mitr_live_... -- npx -y @mitr-analytics/mcp

3. Restart the assistant and ask a question. The dashboard shows when the key was last used.

Tools

There is deliberately no tool to delete anything, edit alerts or webhooks, or manage your team.

Security and privacy

• A key sees what you see. It has the same read access to your workspace as you do in the dashboard. Treat it like a password.

• Revoke it any time under Settings → API keys. It stops working immediately.

• It sits in your assistant's config file in plain text. Use a separate key per tool, so you can revoke one without breaking the others.

• Your AI provider sees the data you ask about. Reports and recent events (page paths, UTM tags, device and location summaries, any custom event properties you send) are returned to the assistant, so they are covered by that provider's terms. Mitr itself identifies visitors only by hashed identifiers; see how we count visitors without cookies.

• add_app returns the new app's SDK secret key, which will then appear in your conversation. Rotate it if you share the transcript.

• The key is only ever sent over HTTPS (plain http:// is accepted only for localhost).

Troubleshooting

Run npx -y @mitr-analytics/mcp --version in a terminal. If that prints a version, the package works and the problem is in the client config.

Configuration

Development

npm install
npm test                                        # builds, then unit tests + an end-to-end stdio test against a stub API
npx @modelcontextprotocol/inspector node dist/index.js   # try the tools by hand (set MITR_API_KEY first)

Questions or problems: support@mitranalytics.dev

License

MIT