The Mixpanel connector.
Segmentation, funnels and retention reports. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Mixpanel exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Mixpanel defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Mixpanel tool
6 tools, named as the agent sees them.
- run_event_segmentationread
Run a segmentation query for ONE event over a date range: counts (or unique users) per interval, optionally split by a property. Use this for "how many X happened last month" or "sign-ups by plan". Use get_top_events first if you do not know the exact event name — the name must match exactly.
- list_funnelsread
List the saved funnels in the project with their funnel_id and name. Call this first to find the funnel_id that get_funnel_report needs — funnels can only be queried by saved id, not defined ad hoc.
- get_funnel_reportread
Get conversion data for one saved funnel over a date range: per-step counts, step conversion ratios, overall conversion, and average time between steps. Get the funnel_id from list_funnels.
- get_retention_reportread
Get a cohort retention report: of the users who first did `born_event` in each period, how many came back and did `event`. Use retention_type 'birth' (first-time cohorts, needs born_event) or 'compounded' (recurring usage).
- list_cohortsread
List the saved cohorts in the project: id, name, description, current member count, creation date, and visibility. Use the returned cohort id with segmentation `where` expressions to scope a query to that audience.
- get_top_eventsread
Get today's highest-volume events with their counts and the percent change from yesterday. Use this to discover the exact event names this project uses before calling run_event_segmentation, or to spot a sudden volume drop.
Use it from any agent
The same Mixpanel tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Mixpanel Service Account Secret in your Mixpanel account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Mixpanel once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.