Mixpanel MCP Server Cursor IDE Setup 2026: Official Remote Endpoint & OAuth

Mixpanel's official MCP server is a hosted, remote endpoint — there's nothing to install and run locally. Point Cursor at https://mcp.mixpanel.com/mcp (or your region's equivalent) through the mcp-remote bridge, authorize once through Mixpanel's own OAuth login in your browser, and Cursor can query funnels, retention, cohorts, and dashboards without you ever pasting a raw API secret into mcp.json.

That's the headline difference from most analytics integrations on this site: no API key to generate, rotate, or accidentally commit. The trade-off is that the server exposes over 50 tools spanning read and write operations — including creating and modifying dashboards — so "no key to manage" doesn't mean "nothing to think about."

Is There Actually an Official Mixpanel MCP Server?

Yes. Mixpanel shipped this as a public beta, announced on its own blog and documented at docs.mixpanel.com/docs/mcp. It isn't a community wrapper around the Mixpanel API — it's a first-party hosted service Mixpanel operates and updates directly, which matters for a tool that can read and modify product analytics data across an entire organization.

What the Mixpanel MCP Server Can Do

The tool surface is large enough that Mixpanel groups it into categories rather than a flat list:

That range is why this is worth setting up even if you only care about one corner of it: a single connection covers "what's our week-4 retention for the March cohort" and "create a dashboard for the new onboarding funnel" without switching tools.

Prerequisites

Step 1: Confirm MCP Is Enabled for Your Org

Before touching Cursor, check Settings → Org → Overview in Mixpanel. If MCP shows as disabled and you're not an org admin, this is a one-message ask to whoever is — there's no per-user opt-in that bypasses the org-level switch. Skipping this step is the most common reason the OAuth flow in Step 3 fails with an access error that looks like a Cursor problem but isn't.

Step 2: Pick Your Region Endpoint

Mixpanel runs three separate regional deployments, each with its own MCP endpoint:

Your project's data residency — set when the project was created — determines which one you need. Pointing Cursor at the wrong region fails authentication in a way that's easy to mistake for a broken OAuth setup, when the actual problem is a US config against an EU project. Check your project's region in Mixpanel's project settings before configuring anything below.

Step 3: Add the Server to ~/.cursor/mcp.json

The interactive OAuth path is what Mixpanel recommends for most people. The mcp-remote bridge handles the browser-based login and token storage so you don't need to manage anything yourself:

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

Swap in https://mcp-eu.mixpanel.com/mcp or https://mcp-in.mixpanel.com/mcp if that's your project's region. Save the file.

Step 4: Restart Cursor and Complete OAuth

Restart Cursor fully. When the mixpanel server first tries to connect, mcp-remote opens a browser window pointed at Mixpanel's own login (https://{mixpanel_domain}/oauth/authorize, using Authorization Code + PKCE — no client secret exposed to Cursor at all). Sign in with your existing Mixpanel credentials and approve the requested scopes: projects analysis events insights segmentation retention data:read funnels flows data_definitions.

Once approved, the token is cached locally and Cursor won't prompt again until it expires or you revoke access from Mixpanel's side. Test with:

List the Mixpanel projects I have access to

Real project names coming back confirms the connection. An empty result usually means your Mixpanel account doesn't have access to any projects under this org, not a broken config — check your Mixpanel role first.

Alternative: Service Account for Headless or CI Use

The interactive OAuth flow assumes a human sitting at a browser. For CI pipelines, scheduled reports, or any automation where no one is available to click through a login, Mixpanel supports service accounts instead:

1. In Mixpanel, go to Organization settings (or Project settings, for a project-scoped account) and create a service account
2. Encode the service account's username and secret as base64, following the same basic-auth convention Mixpanel's own API already uses
3. Pass the encoded string in a custom header instead of going through the browser flow:

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

The practical trade-off: OAuth ties every action to a real person's existing Mixpanel permissions and is trivially revocable by disabling that user or the authorization from Mixpanel's side. A service account is a standing credential with its own permission scope — convenient for automation, but it's a secret you now have to store and rotate like any other, and it doesn't inherit the natural "this person left the company, access is gone" boundary that OAuth gets for free. Default to OAuth for anything a person is actually driving from Cursor; reserve service accounts for genuinely unattended jobs.

Practical Workflows

Ground a roadmap discussion in real retention numbers

Pull week-4 retention for users who signed up in the last 60 days, 
broken down by acquisition channel, before we decide which channel 
to invest more in

Debug a metric that looks wrong in a dashboard

Run the same query as our "Weekly Active Users by Plan" dashboard 
but for just the last 7 days, and show me the raw event counts 
behind it so I can check if the dashboard's filter is doing 
something unexpected

Build a dashboard without leaving the editor

Create a new Mixpanel dashboard called "Onboarding Funnel v2" with 
a funnel report for signup → email verified → first project created, 
segmented by whether the user came from an invite

Check a cohort before referencing it in code

List the events and properties that exist for the "power users" 
cohort definition, so I can make sure the feature flag targeting 
logic I'm about to write actually matches Mixpanel's definition

Tool Categories and What They're Actually For

The Discovery tools (Projects, Events, Properties, Entities, Issues, Lexicon) exist to keep the model from guessing event or property names — a common failure mode with analytics MCP servers is an AI confidently generating a query against user_signed_up when your actual event is Signup Completed. Ask Cursor to list your project's lexicon before writing a query cold, and it grounds every subsequent question in real event names instead of plausible-sounding ones.

The Data Management tools (bulk edits, tag management, duplicate detection) are write-capable and worth treating with the same caution as any write tool on this site — a bulk property edit across millions of events is not something you want approved without reading exactly what it's about to change.

Rate Limits and Beta Features

Mixpanel caps usage at 600 MCP requests per hour per user — generous for interactive chat use, but worth knowing if you're chaining several tool calls per prompt or running scripted analysis through the same connection. The Experiments and Feature Flags tool categories are currently in beta, meaning behavior and tool names there are more likely to shift than the core Analytics and Discovery tools.

When Not to Use This

If your org runs Mixpanel under a HIPAA-compliant configuration, the MCP server currently doesn't support that compliance tier — don't wire this into a workflow touching regulated health data until Mixpanel documents HIPAA support explicitly. Audience targeting and cohort editing are also unavailable through MCP as of this beta; if your actual task is building or modifying a targeting audience, that still has to happen in Mixpanel's UI, not through a chat prompt.

More generally: if your only need is a handful of numbers checked once a week, a saved Mixpanel dashboard link is simpler than setting up OAuth and a local bridge process. Where this earns its keep is ad hoc, developmental use — questions that don't map to an existing saved report, asked in the middle of a debugging session or a roadmap conversation where tabbing to the Mixpanel UI would break your flow.

Troubleshooting

OAuth window opens but authorization fails
Confirm MCP is actually enabled for your org under Settings → Org → Overview. A disabled org-level switch produces an authorization failure that looks like a broken OAuth client, not a permissions setting.

Connects fine but every query returns empty
Check that you're hitting the right regional endpoint. A US-region login against an EU project's data (or the reverse) authenticates successfully but returns nothing meaningful, since the account has no visibility into a project living in a different region's deployment.

mcp-remote process starts but Cursor shows no tools
Confirm Node.js 18+ and that npx resolves on your PATH. Run the exact command from your mcp.json manually in a terminal to see the raw error before assuming Cursor's side is broken.

Service account requests get rejected
Double-check the base64 encoding was applied to the correct username:secret pair and that the header is literally Bearer Basic <encoded value> — a missing "Basic" segment or an incorrectly encoded string fails auth in a way that's easy to misdiagnose as a revoked credential.

Hitting the rate limit during heavy use
600 requests/hour/user is per-user, not per-org — if you're sharing a service account across a team's automation, usage pools together and can hit the ceiling faster than a single interactive user would. Split high-volume automation across separate service accounts if this becomes a bottleneck.

Frequently Asked Questions

Q: Do I need to generate an API key for Mixpanel's MCP server?
A: No, not for the recommended path. The interactive setup uses OAuth through your existing Mixpanel login via the mcp-remote bridge — no key to create, paste, or rotate. Service accounts (for headless automation) use a base64-encoded credential pair instead of a traditional API key.

Q: Which regional endpoint should I use?
A: Whichever matches your Mixpanel project's data residency — US (mcp.mixpanel.com), EU (mcp-eu.mixpanel.com), or IN (mcp-in.mixpanel.com). Check your project settings in Mixpanel; using the wrong region authenticates but returns no usable data.

Q: Can the AI create or modify feature flags and experiments through this connection?
A: Those tool categories exist but are currently in beta, per Mixpanel's own documentation, meaning behavior and exact tool names are more likely to change than the core analytics tools.

Q: Can the AI edit my cohorts or audience targeting?
A: No — audience targeting and cohort editing are explicitly unavailable through the MCP server as of this beta. Cohorts can be read and referenced in queries, but building or modifying one still requires Mixpanel's UI.

Q: Is there a request limit I should plan around?
A: Yes, 600 MCP requests per hour per user. That's rarely a problem for interactive Cursor use but worth watching if a service account is shared across a team's automated jobs, since usage pools per credential rather than per person.

Related Guides

Official docs cited