Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Run funnel, retention and segmentation queries, build boards and edit your Lexicon.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Mixpanel MCP server connects a Mixpanel product-analytics project to Claude, ChatGPT, Cursor and any MCP-compatible agent. It runs funnel, retention, flow and segmentation queries, builds boards, edits Lexicon metadata and triages data-quality issues. Sign-in is OAuth against your own Mixpanel account, so your existing project roles decide what the agent can reach.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Usually yes. Mixpanel states that an organization admin must enable MCP under Settings, Org, Overview before anyone in the organization can connect, and that changes take up to 15 minutes to apply. The exception is free and growth accounts created after 1 August 2026, where MCP is on by default and an admin can still switch it off.
No. Mixpanel states that users authenticate with their own Mixpanel credentials, so existing project permissions and roles stay in effect and users reach only projects they could already open. The same holds for the service account path, where the account's own project roles apply. Connecting does not widen your access.
Mixpanel documents a single limit for the connector: a maximum of 600 MCP requests per hour per user. That is a per-user ceiling rather than a per-organization one. Mixpanel's separate Query API carries a different and tighter limit of 60 queries per hour with at most 5 concurrent queries, documented on its REST reference pages.
Your cached authorization token was issued against an older scope list. Mixpanel's fix is to delete the .mcp-auth folder in the directory where you originally ran the authorization command, then authorize again so a fresh token picks up the current scopes. Mixpanel expanded its published scope list over time, which is what strands older tokens.
Yes, through service accounts, which Mixpanel labels beta. A service account is a non-human Mixpanel user that authenticates with a static base64 header instead of an OAuth flow, intended for CI pipelines and shared setups. Creating one needs Owner or Admin permissions, and the account reaches only projects it has been added to.
No. Mixpanel states plainly that the MCP server does not currently support HIPAA requirements and that its business associate agreement does not cover the feature. Mixpanel also notes that your data is sent to whichever AI provider you connect, so review that provider's handling policies before pointing the connector at regulated data.
No tool in either the directory listing or Mixpanel's published tool reference deletes event data or user profiles. Mixpanel's deletion endpoints for profiles, profile properties and raw events live in its Ingestion API, which the connector does not expose. The connector's delete verbs act on tags, dashboards and cohorts instead.
https://docs.mixpanel.com/docs/features/mcp, which 308-redirects here. The redirect target is cited as canonical. · retrieved 2026-08-18docs.mixpanel.com/robots.txt — Content-Signal: ai-train=yes, search=yes, ai-input=yes (fetched 2026-08-18). Mixpanel expressly permits AI synthesis of this content. · retrieved 2026-08-18https://mcp.mixpanel.com/.well-known/oauth-protected-resource/mcp (fetched 2026-08-18) · retrieved 2026-08-18https://mcp.mixpanel.com/.well-known/oauth-authorization-server/mcp (fetched 2026-08-18) · retrieved 2026-08-18initialize returning HTTP 401 with a WWW-Authenticate header naming the descriptor — 2026-08-18 · retrieved 2026-08-18Connect Mixpanel once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.