Mixpanel MCP Server

The Mixpanel MCP server is the official, provider-hosted Model Context Protocol endpoint that lets AI assistants like Claude, Cursor, ChatGPT, Gemini, and Notion query Mixpanel project data using natural language. Rather than building dashboards or writing report definitions by hand, users can ask product analytics questions and get answers backed by their actual events, properties, cohorts, and saved reports. The server supports both read and write operations, meaning agents can not only run insights, funnels, flows, and retention analyses but also create and edit dashboards, manage lexicon entries, dismiss issues, and configure experiments and feature flags.

Authentication is handled via OAuth 2.0 (Authorization Code + PKCE/S256), so users sign in with their Mixpanel credentials and inherit their existing project permissions. The server is regionally hosted (US, EU, IN), enforces a 600 requests/hour-per-user rate limit, and must be explicitly enabled by an organization administrator before it can be used. Session replay data is exposed alongside event data through a dedicated tool, making it possible to combine quantitative analysis with replay context in a single agent workflow.

Notable capabilities include a unified Run-Query tool that handles insights, funnels, flows, and retention through a single JSON schema (discoverable via Get-Query-Schema), full dashboard CRUD, and beta tools for managing experiments and feature flags. Because the server is hosted by Mixpanel, there is no code to deploy or maintain: clients simply point at the regional URL and complete the OAuth flow.

Tools

Prerequisites

• A Mixpanel account with access to one or more projects
• An organization admin must enable MCP in Settings → Organization → Overview (changes take ~15 minutes to propagate)
• Node.js installed (for clients that use mcp-remote as a proxy)

Regional endpoints

Claude (claude.ai)

Use the official connector in the Claude connector directory and complete the OAuth flow. EU/IN users should add a custom connector pointing at the regional URL.

Cursor

Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.mixpanel.com/mcp"]
    }
  }
}

Claude Desktop

Edit claude_desktop_config.json:

{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.mixpanel.com/mcp"]
    }
  }
}

Gemini CLI

gemini mcp add mixpanel npx -y mcp-remote https://mcp.mixpanel.com/mcp

Codex / Notion / other clients

Add a custom MCP server of type "Streamable HTTP" and enter the regional URL. Authorize via OAuth when prompted.

Notes

• Rate limit: 600 requests/hour per user
• Required OAuth scopes: projects analysis events insights segmentation retention data:read funnels flows data_definitions
• The MCP server does not currently support HIPAA requirements

• Ask conversational questions over Mixpanel data ("What was retention for users who completed onboarding last month?") without building a dashboard
• Generate and save funnel, flow, and retention reports through an agent, then publish them to a shared dashboard via Create-Dashboard
• Investigate a specific user by pulling their event timeline plus session replays via Get-User-Replays-Data
• Audit and clean up the data lexicon: find issues, edit event/property descriptions, manage tags, and dismiss resolved items
• Manage experiments and feature flags from an AI coding assistant alongside product analytics

• "Run a funnel from Signup to Activated for the last 30 days, broken down by plan, and save it to a new dashboard called Q2 Activation."
• "Show retention for users who triggered Onboarding Completed, weekly for the past 8 weeks."
• "Pull the last 5 session replays for distinct_id user_4821 along with their key events."
• "List all events tagged deprecated in project 12345 and dismiss their governance issues."
• "Create a feature flag called new-checkout-flow with a 10% rollout in our Production project."

• Official, provider-hosted server: no infrastructure to run, no community fork to vet
• Broad tool coverage including queries, dashboards, lexicon governance, session replays, and experiments/feature flags
• OAuth 2.0 with PKCE plus inheritance of existing project permissions, with admin opt-in required at the org level
• Regional endpoints for US, EU, and India

• Does not currently support HIPAA workloads
• Rate limited to 600 requests/hour per user, which can constrain large agent workflows
• Requires an organization admin to enable MCP before any user can connect, with ~15 minute propagation delay
• Experiments and feature flag tools are still beta

• Amplitude MCP for similar product analytics querying on Amplitude data
• PostHog MCP for open product analytics, feature flags, and session replays
• Community dragonkhoi/mixpanel-mcp GitHub server, an unofficial alternative if you prefer a self-hosted implementation