PRODUCT ANALYTICS / Mixpanel
Mixpanel MCP
Investigate events and funnels and manage Mixpanel reports, Lexicon and experiments with existing project permissions.
“Mixpanel MCP Server”
01 / THE REASONING
Why this made the selection.
- Provides query schemas alongside analytics and content-management tools.
- Documents region-specific endpoints and distinct interactive/service-account authentication.
- Mixpanel’s docs say each user connects with their own credentials and can only see projects they already have access to.
- The product page says this MCP is not read-only and can write, but still cannot grant access beyond the connected user’s permissions.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://docs.mixpanel.com/docs/mcp
- https://mixpanel.com/ai/mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- Current setup documentation qualifies the older marketing statement that every organization needs manual enablement.
- Service-account authentication is beta and separate from the shown interactive OAuth path.
- Once MCP is enabled, Mixpanel users authenticate with their own credentials. Existing project permissions apply, and users can only see projects they already have access to.
- The product page says Mixpanel MCP is not limited to read-only analytics: it can write objects such as dashboards, but only within what the connected user is already allowed to do.
- Successful mutating calls can appear in the audit log with an MCP origin. The docs page says read-only and failed tool calls are not logged.
- Experiments/flags and audit-log tools have separate beta limitations; audience targeting and cohort editing are not supported by the documented beta tools.
Not established by this review
- Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Confirm organization MCP enablement; new free/growth accounts after August 1, 2026 are enabled by default, while other accounts need an administrator.
- Select US, EU or India endpoint and complete OAuth as the intended user.
- Inspect projects/events first and include explicit dates in analytical requests.
- Check organization MCP enablement, select the correct data region and confirm beta access before depending on those tools in automation.
Before you start
- A Mixpanel account with project access and OAuth-capable HTTP MCP client.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"mixpanel": {
"type": "http",
"url": "https://mcp.mixpanel.com/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.mixpanel.com/docs/mcp
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
https://mixpanel.com/ai/mcp
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports