Mixpanel MCP Server

About

Mixpanel MCP server for read-only product analytics. Mixpanel itself publishes no MCP server — its agent tooling ships as the mixpanel-headless Python CLI and a set of Claude Agent Skills — so the de-facto server for this API is dragonkhoi/mixpanel-mcp, the community project with the most adoption at 19 stars and 19 forks. It exposes 19 tools over Mixpanel's Query API and nothing over the ingestion API, so an assistant can read your data but cannot write events or edit profiles. Coverage is broad for a single-file server: saved Insights, Funnel and Retention reports (query_insights_report, query_funnel_report, query_retention_report, plus list_saved_funnels and list_saved_cohorts to find the IDs), five segmentation tools including numeric bucketing and per-unit-time sum and average, event and property discovery (get_top_events, get_today_top_events, top_event_properties, top_event_property_values), profile lookup via query_profiles and profile_event_activity, and custom_jql for anything the typed tools do not cover. Authentication is a Mixpanel Service Account username and password plus a project ID, sent as HTTP Basic on every request. There is no published npm package: the project's package.json claims the name mcp-mixpanel, but that name was unpublished from npm in April 2025 and has not existed since, so install is either a git clone and build or the Smithery bundle. Every API URL is hardcoded to mixpanel.com, which means EU- and India-residency projects are not supported. Last commit March 2025.

Installation

git clone https://github.com/dragonkhoi/mixpanel-mcp && cd mixpanel-mcp && npm install && node build/index.js SERVICE_ACCOUNT_USERNAME SERVICE_ACCOUNT_PASSWORD PROJECT_ID

Setting up dragonkhoi/mixpanel-mcp

1. 1.Create a Mixpanel Service Account

   The server authenticates with HTTP Basic against Mixpanel's Query API, and the credential is a Service Account — not your login, and not a project token. Create one in Organization Settings → Service Accounts. Mixpanel shows the secret exactly once. The README calls the two halves "username" and "password"; in the Mixpanel UI they are labelled username and secret, which is the single most common point of confusion on the issue tracker. You also need the numeric project ID, which lives in Project Settings, not in Organization Settings.

2. 2.Clone and build

   There is no package to npx. The repo's package.json runs the TypeScript build from a postinstall hook, so `npm install` alone produces build/index.js and marks it executable.

   bash

   git clone https://github.com/dragonkhoi/mixpanel-mcp
   cd mixpanel-mcp
   npm install

3. 3.Point your client at the build, with credentials as positional arguments

   The three credentials are read from argv, in the order username, password, project ID. Use the absolute path to build/index.js — a relative path resolves against whatever directory your MCP client happens to launch from.

   claude_desktop_config.json

   {
     "mcpServers": {
       "mixpanel": {
         "command": "node",
         "args": [
           "/ABSOLUTE/PATH/TO/mixpanel-mcp/build/index.js",
           "YOUR_SERVICE_ACCOUNT_USERNAME",
           "YOUR_SERVICE_ACCOUNT_SECRET",
           "YOUR_PROJECT_ID"
         ]
       }
     }
   }

4. 4.Or run the Smithery bundle instead of building

   Smithery hosts a prebuilt stdio bundle of the same project. Its config schema takes the same three fields under the names username, password and projectId. This is the route the README recommends for Cursor, where a single command string is easier to paste than a JSON args array.

   bash

   npx -y @smithery/cli@latest run @dragonkhoi/mixpanel-mcp \
     --config '{"username":"YOUR_USERNAME","password":"YOUR_SECRET","projectId":"YOUR_PROJECT_ID"}'

5. 5.Confirm it is reading the right project

   Ask for today's top events before anything else. It is the cheapest call in the set and it fails loudly on all three credential mistakes: a wrong username or secret returns a 401, and a wrong project ID returns an empty list rather than an error — which is why you want to see event names you recognise, not just an absence of red text.

All 19 tools

Read-only, every one of them. These map onto Mixpanel's Query API; the ingestion API — track, engage, import — is not exposed at all, so no prompt can make this server write to your project. Tool names and descriptions were read from src/index.ts and cross-checked against the built server's advertised tool list in the Smithery registry.

What people use it for

Which one should you use?

Three community servers share this name and they are not substitutes for each other. Pick by direction of data flow first, then by whether you can tolerate a clone.

Categories

Works With

Frequently Asked Questions

Related Guides