Mixpanel MCP Server

​

Overview

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

​

Connecting to the MCP Server

• OAuth — Users sign in through a browser with their Mixpanel credentials. Best for interactive use in AI assistants like Claude, ChatGPT, or Cursor.
• Service Accounts (Beta) — A static credential header with no browser login required. Best for CI/CD pipelines, automated agents, and shared team setups.

​

Connecting with OAuth

​

Claude

​

Claude Code

claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp

​

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

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

codex mcp login mixpanel

​

Notion

1. Create a new Agent from the Agents section in the Notion sidebar
2. In the Agent’s Settings, go to Tools and Access → + Add Connection
3. Select Mixpanel and complete the OAuth flow

​

Gemini CLI

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

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

​

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

​

Microsoft Copilot (JSON-configured clients)

​

Connecting with Service Accounts

​

Prerequisites

1. Create a service account in your Organization settings or Project settings. You need Owner or Admin permissions to do this.
2. Save the username and secret — you won’t be able to view the secret again after creation.
3. Ensure the service account has access to the projects you want to query via MCP.
4. MCP must be enabled by an org admin in Settings → Org → Overview.

​

Generating the Authorization Header

echo -n "<username>:<secret>" | base64

Authorization: Bearer Basic <base64-encoded-credentials>

echo -n "my-sa.abc123.mp-service-account:my-secret" | base64
# Output: bXktc2EuYWJjMTIzLm1wLXNlcnZpY2UtYWNjb3VudDpteS1zZWNyZXQ=

​

Claude

{
  "mcpServers": {
    "mixpanel": {
      "url": "https://mcp.mixpanel.com/mcp",
      "headers": {
        "Authorization": "Bearer Basic <base64-encoded-credentials>"
      }
    }
  }
}

​

Claude Code

claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp \
  --header "Authorization: Bearer Basic <base64-encoded-credentials>"

{
  "mcpServers": {
    "mixpanel": {
      "type": "http",
      "url": "https://mcp.mixpanel.com/mcp",
      "headers": {
        "Authorization": "Bearer Basic ${MIXPANEL_SA_TOKEN}"
      }
    }
  }
}

​

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
4. Add the authorization header and click Save

​

Codex CLI

[mcp_servers.mixpanel]
url = "https://mcp.mixpanel.com/mcp"
headers = { Authorization = "Bearer Basic <base64-encoded-credentials>" }

​

Notion

​

Gemini CLI

gemini mcp add mixpanel npx -y mcp-remote https://mcp.mixpanel.com/mcp \
  --header "Authorization:Bearer Basic <base64-encoded-credentials>"

{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.mixpanel.com/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer Basic <base64-encoded-credentials>"
      }
    }
  }
}

​

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": {
      "url": "https://mcp.mixpanel.com/mcp",
      "headers": {
        "Authorization": "Bearer Basic ${env:MIXPANEL_SA_TOKEN}"
      }
    }
  }
}

3. Set the MIXPANEL_SA_TOKEN environment variable to your base64-encoded credentials

​

Microsoft Copilot (JSON-configured clients)

​

Example Queries

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

• “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 a board of purchase metrics”
• “Build a weekly growth dashboard with signups, activations, and churn”

• “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”

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

• “Create an experiment to test whether showing a progress indicator during onboarding increases activation rate”
• “Create a feature flag for our new AI-powered search”
• “How did our checkout experiment perform? Did it reach significance?”

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

​

Security Considerations

• 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

• 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.

​

Rate Limits

• A maximum of 600 MCP requests/hour per user

​

Building Custom Integrations (OAuth)

​

OAuth Discovery

https://mcp.mixpanel.com/.well-known/oauth-protected-resource/mcp

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

/.well-known/oauth-protected-resource
/.well-known/oauth-authorization-server

​

Dynamic Client Registration

​

Authorization Code Flow with PKCE

• 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

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

dashboard_reports bookmarks user_details business_context