The Mixpanel MCP server is a hosted Model Context Protocol server that lets an AI assistant query and manage your Mixpanel data in natural language. Connect it from Claude Code, Cursor or Codex with one URL and a Mixpanel sign-in.
What the Mixpanel MCP server exposes
The server reads and writes. An agent can run analyses, and it can also create, update and delete dashboards, cohorts and Lexicon entries. The documented tools group into these categories:
- Analytics: Run-Query for insights, funnels, flows and retention, plus Get-Report for saved reports.
- Dashboards: create, list, get, update, duplicate and delete.
- Data discovery: Get-Projects, Get-Events, List-Properties, Get-Property-Values and Search-Entities.
- Data management in Lexicon: edit events and properties, manage tags, find and merge duplicates, and keep tracking plans.
- Custom properties, cohorts, lookup tables and metrics: create, read and update each.
- Session replays: Get-User-Replays-Data analyzes one user's replays next to their events.
- Experiments and feature flags: open beta.
- Agent Intelligence: beta, for organizations that have it enabled.
- Audit log: Get-Audit-Log shows who changed what, and when.
A typical session goes in four steps: discover your projects and events, run a query, create a dashboard or clean up Lexicon, then refine with follow-up questions in the same conversation.
Set up the Mixpanel MCP server in Claude Code
Pick the URL for your project's region:
- US:
https://mcp.mixpanel.com/mcp
- EU:
https://mcp-eu.mixpanel.com/mcp
- IN:
https://mcp-in.mixpanel.com/mcp
For a US project, add the server with one command:
claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp
Then run /mcp inside Claude Code and finish the Mixpanel OAuth flow in your browser. Claude Code's MCP docs cover managing the server afterwards.
Mixpanel also ships a Claude Code plugin with guided workflows on top of the connection:
claude plugin marketplace add mixpanel/ai-plugins
claude plugin install mixpanel
Run /mixpanel:install inside Claude Code once per project.
Set up Mixpanel MCP in Cursor and Codex
Cursor
Open Settings, then Tools & MCP, then New MCP Server. That opens ~/.cursor/mcp.json. Add:
{
"mcpServers": {
"mixpanel": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.mixpanel.com/mcp"]
}
}
}
Save the file and Cursor prompts you to authorize with Mixpanel on first connect. For EU or IN projects, swap in the regional URL. See Cursor's MCP docs for project-level config.
Codex
In the Codex CLI, add this to ~/.codex/config.toml:
[mcp_servers.mixpanel]
url = "https://mcp.mixpanel.com/mcp"
Then authorize with codex mcp login mixpanel.
In the Codex app, go to Settings, then MCP Servers, then + Add Server. Name it, choose Streamable HTTP, enter the URL and click Save. More options are in the Codex MCP docs.
Mixpanel MCP authentication and data access
Two methods are supported.
- OAuth signs you in through a browser with your own Mixpanel credentials. It suits interactive use in an assistant.
- Service accounts (beta) use a static header with no browser login. They suit CI/CD pipelines, automated agents and shared team setups.
To use a service account:
- Create one in Organization or Project settings. You need Owner or Admin permissions.
- Save the username and secret. The secret cannot be viewed again.
- Add the account to the projects you want to query.
- Encode the credentials:
echo -n "<username>:<secret>" | base64
- Send the result as the header
Authorization: Bearer Basic <base64-encoded-credentials>.
In Claude Code, pass it with --header:
claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp \
--header "Authorization: Bearer Basic <base64-encoded-credentials>"
To keep the secret out of config files, put Bearer Basic ${MIXPANEL_SA_TOKEN} in the headers block of .mcp.json and set MIXPANEL_SA_TOKEN before starting Claude Code.
Access follows your existing Mixpanel roles. A user sees only the projects they already have access to, and a service account sees only the projects it was added to. If an admin turned on Verified Mode, query results still include every requested entity, and entities not verified in Lexicon are flagged as unverified.
MCP is on by default for free and growth accounts created after August 1, 2026. For every other account, an org admin enables it in Settings, Org, AI Settings, and changes can take up to 15 minutes. Admins can switch it off there too.
Mixpanel MCP limits
These are the limits Mixpanel documents:
- Free plans can be subject to Query API access limits. Mixpanel's pricing for mobile apps explains what each plan includes.
- Bulk-Edit-Events and Bulk-Edit-Properties change up to 50 items per call.
- The Experiments and Feature Flags tools are in open beta and do not support audience targeting, including cohort targeting. Use the Mixpanel UI for that.
- Agent Intelligence tools need that feature enabled for your organization.
- Service-account authentication is in beta.
- Notion's agent connector does not support service accounts.
- The URL must match the region of your project.
A read-only MCP for mobile app analytics
Mixpanel's MCP covers a full product analytics workspace and can change dashboards and Lexicon. ActivationPal takes the narrower route: an MCP server that only reads, built for iOS and Android app teams with native Swift, Android, Flutter and React Native apps. Ask about installs, onboarding drop-off, paywall conversion, revenue, retention and trials, and the agent answers from your real numbers.
MCP is included on every ActivationPal plan, the free one too. Keys are read-only, you choose which apps a key can see, and you can revoke it at any time. It works with Claude Code, Codex, Cursor, OpenCode and Windsurf.
The server is https://activationpal.com/api/mcp over streamable HTTP, with a Bearer key from the dashboard. It exposes five tools: list_apps, get_stats, get_cohorts, get_events and get_user. In Claude Code:
claude mcp add --transport http activationpal https://activationpal.com/api/mcp --header "Authorization: Bearer <key>"
In Cursor or Codex, add a server with the name activationpal, the transport Streamable HTTP, that URL and an Authorization header carrying your key. The agent API guide has the full setup. Weighing the field first? See Mixpanel alternatives for mobile apps.