Model Context Protocol server for Rollbar
Mixpanel is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Query Mixpanel events, funnels, retention, segmentation and insights (JQL).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-mixpanel-mcp https://mixpanel.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# mixpanel_top_events, mixpanel_segmentation, mixpanel_retention and 4 more
Mixpanel costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-mixpanel-mcp https://mixpanel.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List today's top events with counts and % change vs yesterday. Good first call to discover what events a project tracks. Query API: GET /events/top.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | general (totals), unique (per-user), or average. Default general. |
| limit | integer | no | Max events to return. Default 100. |
Count/segment/filter a single event over a date range. e.g. 'Signed up' by country last week. Params on/where use Mixpanel segmentation expressions like properties["$country_code"]. Query API: GET /segmentation. (Upstream maintenance mode — for saved reports prefer mixpanel_query_insights.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | Single event name to analyze (not an array). |
| from_date | string | yes | Start date yyyy-mm-dd (inclusive). |
| to_date | string | yes | End date yyyy-mm-dd (inclusive). |
| on | string | no | Property expression to segment on, e.g. properties["$city"]. |
| where | string | no | Filter expression, e.g. properties["$os"]=="iOS". |
| unit | string | no | Bucket size. Default day. |
| type | string | no | general | unique | average. Default general. |
| limit | integer | no | Top N property values (only if on set). Default 60. |
Cohort retention: of users who did born_event, how many came back and did event over subsequent intervals. Query API: GET /retention.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | yes | Start date yyyy-mm-dd (inclusive). |
| to_date | string | yes | End date yyyy-mm-dd (inclusive). |
| retention_type | string | no | birth = first-time retention (default), compounded = recurring. |
| born_event | string | no | The defining first event for a birth cohort. Required when retention_type=birth. |
| event | string | no | Returning event to measure. If omitted, any event counts. |
| born_where | string | no | Filter expression applied to born_event. |
| where | string | no | Filter expression applied to the returning event. |
| interval | integer | no | Units per bucket (<=90 if days). Default 1. |
| interval_count | integer | no | Number of intervals to report. |
| unit | string | no | Interval unit. Default day. |
Get the funnel_id and name of every saved funnel in the project. Query API: GET /funnels/list.
No parameter schema on file.
Get conversion data for a saved funnel (use mixpanel_list_funnels to find funnel_id). Query API: GET /funnels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| funnel_id | integer | yes | Saved funnel id (from mixpanel_list_funnels). |
| from_date | string | yes | Start date yyyy-mm-dd (inclusive). |
| to_date | string | yes | End date yyyy-mm-dd (inclusive). |
| length | integer | no | Conversion window length. |
| length_unit | string | no | Unit for length. |
| interval | integer | no | Number of days per bucket. |
| unit | string | no | Bucketing unit. |
| limit | integer | no | Limit on segmentation breakdown. |
Fetch the computed data behind a saved Insights report by bookmark_id (the report id in the board URL). Mixpanel's recommended, non-deprecated path for programmatic reporting. Query API: GET /insights.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bookmark_id | integer | yes | Insights report id (bookmark_id) from the report URL. |
| workspace_id | integer | no | Workspace id, if applicable. |
Run a custom JQL (JavaScript Query Language) script for arbitrary analysis. Power-user escape hatch. Script must define main(). Query API: POST /jql. (Upstream maintenance mode; 2-min timeout, 5GB/query limit.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| script | string | yes | JQL script defining function main(){ ... } that returns rows. |
| params | string | no | Optional JSON string exposed to the script as the params global. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mixpanel or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| mixpanel_top_events | no tags | |
| mixpanel_segmentation | no tags | |
| mixpanel_retention | no tags | |
| mixpanel_list_funnels | no tags | |
| mixpanel_query_funnel | no tags | |
| mixpanel_query_insights | untrusted-input | untrusted-input: keyword "fetch" |
| mixpanel_jql | code-exec | code-exec: parameter "script" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mixpanel can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.