Provides tools for querying Mixpanel analytics data, including event data with counts and properties, funnel conversion rates, and user retention cohort data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-mixpanel show signup funnels and retention for last 30 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mixpanel MCP — wraps Mixpanel Data Export API (mixpanel.com/api)
Part of Pipeworx — an MCP gateway connecting AI agents to 1573+ live data sources.
Tool | Description |
| Query event data from Mixpanel for a date range. Returns event counts and properties. Example: get_events({ from_date: "2024-01-01", to_date: "2024-01-31", event: "Sign Up", _apiKey: "your_api_secret" }) |
| Get funnel conversion data from Mixpanel. Shows step-by-step conversion rates. Example: get_funnels({ funnel_id: "12345", from_date: "2024-01-01", to_date: "2024-01-31", _apiKey: "your_api_secret" }) |
| Get user retention cohort data from Mixpanel. Shows how many users return over time. Example: get_retention({ from_date: "2024-01-01", to_date: "2024-01-31", _apiKey: "your_api_secret" }) |
Related MCP server: Mixpanel MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mixpanel": {
"url": "https://gateway.pipeworx.io/mixpanel/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/mixpanel/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1573+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"mixpanel": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-mixpanel"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-mixpanelIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Mixpanel data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Agent-Native Amplitude/Mixpanel - connect data sources, prompt for charts
Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.
Let AI agents query data and act across all your business apps via MCP.
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
