Mixpanel MCP: Setup, Tools and the 600-Request Limit

MCP
Mixpanel MCP: Setup, Tools and the 600-Request Limit

Mixpanel runs an official remote MCP server at https://mcp.mixpanel.com/mcp, with separate EU and India endpoints. It exposes more than 60 tools that query and change dashboards, events, cohorts and experiments, limited to 600 requests an hour per user.

Last updated September 21, 2026. Figures are from Mixpanel's own documentation. New to the protocol? Start with what MCP is.

What the Mixpanel MCP server exposes

Surface What you get
QueriesInsights, funnels, flows and retention, run in natural language
DashboardsCreate, read, update and delete
Data managementEvents, properties, cohorts and lookup tables
Experiments and flagsExperiments and feature flags, in beta
Session replayAnalysis of recorded sessions

The endpoint is https://mcp.mixpanel.com/mcp. People sign in with OAuth; headless connections, such as a pipeline, use service accounts, which are in beta. Use the endpoint for your data region: https://mcp-eu.mixpanel.com/mcp for the EU and https://mcp-in.mixpanel.com/mcp for India.

Connecting it

1. Open your client's connector settings

In Claude, go to Settings, then Customize, then Connectors. In ChatGPT, turn on Developer mode under Settings, then Security and login, and add it under Settings, then Plugins. If Mixpanel is already listed in the client's directory, add it from there instead.

2. Paste the endpoint

Add a custom connector with the URL https://mcp.mixpanel.com/mcp and leave the advanced fields empty. There is no client ID or secret to enter; the server registers itself when you sign in.

3. Sign in and read the scopes

The consent screen is the one place you see what you are granting. Read it, and choose the narrower scopes wherever you are offered a choice.

4. Confirm the tools arrived

Ask the assistant what the connector can do. An empty list after a successful sign-in means the token is not being accepted: disconnect and reconnect to clear the stale grant.

The exact path for thirteen clients is in the MCP client directory.

What it costs

  • Mixpanel lists no separate price for MCP.
  • A hard ceiling of 600 MCP requests an hour per user.
  • Accounts created after August 1, 2026 have it on by default. Older organizations need an admin to enable it under Settings, Org, Overview.

What 600 requests an hour means

Ten a minute, per person. A person asking questions will never notice. An agent asked something open — "why did activation drop last week?" — may run a funnel, break it down by three properties, pull two cohorts and compare retention: a dozen calls before it answers. Put that on a schedule, or let an agent iterate, and the ceiling arrives in minutes. The symptom is a model that stops halfway through an analysis.

The limits worth knowing

  • Off by default on older accounts. Any organization created before August 2026 needs an admin to switch MCP on. If a teammate says "it does not work", this is usually why.
  • Not covered for HIPAA. Mixpanel states the MCP server does not currently support HIPAA requirements. Health-data projects should not be connected.
  • Permissions carry over, including write access. You reach exactly the projects you can reach in Mixpanel, with the same rights. If you can delete a dashboard in the app, a model acting for you can too.
  • Product data, not spend. Mixpanel sees what users did. It has no view of what acquiring them cost or which campaign paid for it.

Where it stops for marketing

Mixpanel explains behaviour after the sign-up. The questions that move a marketing budget sit before it: which channel, which campaign, which creative, at what cost. Sprites is an AI marketing agent whose MCP server reads the ad accounts on the other side of that line, and proposes the budget change as an approval card.

That is the edge of what one vendor's data can answer, not a flaw in the server. It is why a marketing stack usually runs two or three: this one for what it is good at, and one for the channels that spend money. For the other half: Every ad channel behind one MCP server. If you would rather hand the marketing half to one agent, Sprites runs Google Ads, Meta, LinkedIn and SEO behind one connector, with every write staged for your approval.

Before you grant write access

MCP has no built-in approval step: a write tool applies the moment the model calls it, unless the server itself holds the change. Check three things before you connect: which scopes the consent screen asks for, whether writes are staged or applied, and how to revoke access. The rest is in is MCP safe.

Related

Mixpanel MCP questions

Does Mixpanel have an MCP server?

Yes. Mixpanel runs an official remote server at https://mcp.mixpanel.com/mcp, with EU and India endpoints, signed in with OAuth or, in beta, a service account.

What is the Mixpanel MCP rate limit?

600 MCP requests an hour per user. An agent iterating on an analysis can reach that far faster than a person asking questions.

Why is Mixpanel MCP not working on my account?

Organizations created before August 1, 2026 need an org admin to enable MCP under Settings, Org, Overview. Newer accounts have it on by default.

Can Mixpanel MCP change my dashboards?

Yes. It creates, updates and deletes dashboards and manages events, properties, cohorts and lookup tables, within the permissions you already have in Mixpanel.

Is Mixpanel MCP HIPAA compliant?

No. Mixpanel states the MCP server does not currently support HIPAA requirements.

Whose ads do you want to see next?

Search any brand's ads (Nike, Canva, Ro...)