Mixpanel MCP Server

Overview

Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data. Once connected, you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.

A typical workflow looks like:

1. Discover: Find your projects, events, and properties
2. Query: Run insights, funnels, flows, or retention analyses
3. Create: Build dashboards, organize Lexicon, or manage data quality issues
4. Iterate: Refine with follow-up questions in the same conversation

Available Tools

MCP Server URLs

Permissions & Access

Once enabled, any Mixpanel user in your organization can connect. Users authenticate with their own Mixpanel credentials, so all existing project permissions and roles apply — users can only see data from projects they already have access to.

Connecting to the MCP Server

Claude

• Go to claude.ai/customize/connectors and search for Mixpanel. Click Connect and complete the Mixpanel OAuth flow.
• For EU or IN regions, use Settings → Connectors → Add Custom Connector instead, and enter your MCP Server URL.

ChatGPT

1. Go to Settings → Connectors → Advanced and enable Developer Mode
2. Add a new connector — set the MCP Server URL to your regional endpoint and Authentication to OAuth
3. Complete the Mixpanel OAuth flow
4. Optionally publish the connector to your workspace so teammates can use it

Codex

1. Go to Settings → MCP Servers → + Add Server
2. Provide a name (e.g. Mixpanel) and select Streamable HTTP
3. Enter your MCP Server URL and click Save

Codex CLI

Add the following to ~/.codex/config.toml (use the EU or IN URL if needed):

[mcp_servers.mixpanel]
url = "https://mcp.mixpanel.com/mcp"

Then authorize:

codex mcp login mixpanel

Notion

1. Go to Settings → Connections → + Add custom MCP
2. Enter your MCP Server URL and give it a name
3. Click Connect and complete the Mixpanel OAuth flow

Cursor

1. Go to Settings → Tools & MCP → New MCP Server to open ~/.cursor/mcp.json
2. Add the following (use the EU or IN URL if needed):

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

3. Save the file — Cursor will prompt you to authorize with Mixpanel on first connect

Gemini CLI

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

Or edit ~/.gemini/settings.json manually and add:

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

Other JSON-configured clients

Any client that supports the MCP JSON config format can connect using the same JSON snippet from the Cursor section above. The first time it connects it will prompt you to authorize with Mixpanel.

Example Queries

Once connected, try asking your AI assistant:

Understand your data

• “What projects do I have access to?”
• “What are the most fired events this week?”
• “Which properties on checkout_completed are marked as PII?”

Query & analyze

• “How many sign ups did we have in February?”
• “What’s our signup-to-purchase conversion rate this month vs last month?”
• “Show 7-day retention for users who completed onboarding in Q1”
• “Which acquisition channels have the best 30-day retention?”

Create & build

• “Create a board of purchase metrics”
• “Build a weekly growth dashboard with signups, activations, and churn”

Automate Lexicon work

• “Add descriptions to any events that don’t have one”
• “Tag all checkout-related events with ‘Checkout’”
• “Hide any events that haven’t fired in the last 90 days”
• “Find all properties that look like PII but aren’t flagged yet”

Triage data quality

• “Show me all open data quality issues for the Signup event”
• “Dismiss all issues for events we deprecated last quarter”

Investigate users

• “This user reported a bug — what happened in their last 3 sessions?”
• “Walk me through what [user ID] did before they churned”

Security Considerations

When connected, the AI assistant can both read and write to Mixpanel on your behalf. Your Mixpanel data is also sent to whichever AI provider you’re using (Claude, ChatGPT, etc.), so review that provider’s data handling policies before connecting.

Access controls

• MCP must be explicitly enabled by an org admin. It is off by default
• Users can only access projects they already have permission to view in Mixpanel
• All existing roles and project-level permissions remain in effect

Other considerations

• Check applicable compliance requirements (GDPR, CCPA, etc.) before connecting to projects with personal data
• If using a shared AI environment (e.g., a team workspace), be aware that conversation history may be visible to others

Troubleshooting

• “MCP access is not enabled for this project”: Ask your org admin to enable MCP in Settings → Org → Overview.
• “Missing scope” error: Your cached auth token was created with an outdated scope list. Delete the .mcp-auth folder in the directory where you ran the authorization command, then re-authorize.
• Authorization fails: Ensure your Mixpanel account has access to at least one project and that MCP is enabled at the org level.
• Desktop app doesn’t pick up config changes: Restart the application after editing the config file.

Building Custom Integrations (OAuth)

If you’re building a third-party MCP client or custom integration, use the following OAuth configuration.

OAuth Discovery

Discover the full OAuth configuration at:

https://mcp.mixpanel.com/.well-known/oauth-authorization-server

Dynamic Client Registration

Authorization Code Flow with PKCE

Mixpanel uses Authorization Code + PKCE (S256):

• Authorization endpoint: https://{mixpanel_domain}/oauth/authorize
• Token endpoint: https://{mixpanel_domain}/oauth/token/
• Grant types: authorization_code, refresh_token
• Code challenge method: S256
• Token endpoint auth methods: none, client_secret_basic, client_secret_post

Required OAuth Scopes

Mandatory:

projects analysis events insights segmentation retention data:read funnels flows data_definitions

Optional:

dashboard_reports bookmarks user_details