Mixpanel is an anchor product-analytics platform because its hosted MCP combines behavioral analysis with dashboard construction, Lexicon and data-quality maintenance, cohort and metric management, and beta experiment and feature-flag operations.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Organizations, projects, and workspaces; events and properties; insights, funnels, flows, retention, reports, and session replays; dashboards; Lexicon tags and data-quality issues; business context; custom properties; cohorts; lookup tables; saved metrics; experiments; and feature flags.
Discover organizations, projects, events, properties, values, issues, and saved entities; run insights, funnels, flows, and retention queries; retrieve reports, dashboards, cohorts, lookup tables, metrics, experiments, feature flags, and user replay context.
Create, update, duplicate, and delete dashboards; edit event/property metadata and PII classification; tag, merge, hide, or dismiss governed data entities and issues; update business context; manage custom properties, cohorts, lookup tables, and saved metrics; and create or update beta experiments and feature flags.
The hosted MCP has US, EU, and India endpoints. Interactive users authenticate with Mixpanel OAuth; beta service-account authentication uses a static header for headless use. An organization admin must first enable MCP, and existing project roles and permissions constrain each user or service account.
MCP is off by default and requires organization-admin enablement. Existing Mixpanel roles remain in force, but the server can perform destructive and taxonomy-changing operations. BYO-UI should require preview and confirmation for deletes, merges, PII reclassification, experiment lifecycle changes, and feature-flag targeting.
Maximum 600 MCP requests per hour per user. Service-account authentication and experiment/feature-flag tools are beta; audience targeting and cohort editing for those beta product tools are not supported through MCP. The MCP is not covered by Mixpanel's HIPAA BAA, and connected data is sent to the chosen AI provider.
First-party access
Agent access
Support: Official MCP server
Read scope: Behavioral queries and saved-report retrieval; organization/project discovery; event/property and data-quality inspection; dashboards; cohorts; lookup tables; metrics; experiments and flags; and per-user replay analysis.
Write scope: Dashboards, Lexicon metadata/tags/PII labels, data-quality issues and merges, business context, custom properties, cohorts, lookup tables, saved metrics, and beta experiment/feature-flag configuration can be changed when permissions allow.
Authentication: OAuth with authorization-code plus PKCE for interactive users; beta service-account credentials for headless clients; distinct US, EU, and India MCP endpoints.
Approval boundary: Mixpanel documents an admin enablement gate, not per-operation MCP approvals. Because the catalog includes deletes, merges, PII-classification edits, and flag/experiment changes, BYO-UI should obtain explicit confirmation before those calls.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Mixpanel ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Tool-level reads and writes; US/EU/India deployment; OAuth and beta service accounts; admin enablement; inherited permissions; beta, rate, HIPAA, and provider-transfer limits
Full first-party MCP tool, region, auth, permission, security, and limit review completed 2026-07-22
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Mixpanel's Query API returns calculated report, profile, and cohort results. It is a product query API, not unrestricted SQL over Mixpanel's underlying storage.
Targeted first-party access review
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
