Query Mixpanel events, funnels, retention, segmentation and insights (JQL). Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Mixpanel connector, then ask in plain words. The AI picks the tools.
For product managers and analysts who track user behavior in Mixpanel.
The AI lists today's top events with counts and the change against yesterday. Use it to see what a project tracks and what moved.
The AI counts one event over a date range and splits it by a property such as country, with optional filters. You get sign-ups per day or per segment.
The AI lists the saved funnels of the project and reads the conversion data of one. You see where users drop off.
The AI runs a retention report: of users who did a first event, how many did a second event in later intervals. You see if new users return.
The AI fetches the computed data behind a saved Insights report by its id and explains the numbers. For other questions it can run a custom JQL script.
The login page asks for your Mixpanel project API secret.
Find it in Mixpanel → Project settings → Access keys → API Secret. Your secret is used only to call the Query API on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"mixpanel": {
"url": "https://mixpanel.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"mixpanel": {
"type": "http",
"url": "https://mixpanel.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Mixpanel project API secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Mixpanel server only. Ask your AI to run mixpanel_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with mixpanel_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with mixpanel_upgrade before then undoes the cancel. Or write to [email protected].
mixpanel_top_eventsmixpanel_segmentationmixpanel_retentionmixpanel_list_funnelsmixpanel_query_funnelmixpanel_query_insightsmixpanel_jqlmixpanel_usage_statusmixpanel_request_featuremixpanel_upgrademixpanel_cancel_subscriptionSee today's top events and what changed. Count an event by day or by property. Check conversion in a saved funnel. Measure how many users come back. Read an Insights report or run a custom JQL query. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Mixpanel. The server calls the Mixpanel API with your own Mixpanel access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Mixpanel project API secret. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Mixpanel project API secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Mixpanel API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Mixpanel.
All 7 Mixpanel tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Mixpanel server only. Cancel any time: your paid plan then runs to the end of the paid period. Run mixpanel_usage_status to see how many calls you used.
Ask the AI to run mixpanel_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run mixpanel_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with mixpanel_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.