---
name: "Mixpanel"
description: Query Mixpanel events, funnels, retention, segmentation, and saved insights through Mixpanel's own MCP server.
version: 1
situations: mixpanel, product analytics, funnels, retention, events
requires-secrets:
requires-packages:
requires-connector: mixpanel
---

# Mixpanel

Mixpanel publishes its own MCP server, and that is what you're connected to. Its tools are the
reference — this file is only about using them well.

## Where the tools are

- **On the built-in brain**: your own tool list, prefixed `mcp_mixpanel_…`.
- **On a CLI brain**: that CLI's tool list, under the `mixpanel` server.

The connection is **read-oriented** — the scopes it holds are projects, analysis, events, insights,
segmentation, retention and funnels. It queries data; it does not change it. If you see no Mixpanel
tools, the operator hasn't connected it: **Skill store → Mixpanel → Connect**.

## Getting an answer that is actually true

Product analytics is easy to query and easy to misread, and a confident wrong number is worse than no
number. Before reporting anything:

1. **Name the project.** An account usually has several (prod, staging, a rewrite). The same event
   exists in all of them.
2. **Name the date range**, and prefer a whole number of weeks — most products have a weekday cycle,
   so "the last 10 days" bakes in a weekend distortion.
3. **Check the event actually fires** before drawing a conclusion from its absence. A funnel step at
   zero is far more often a missing instrumentation call than a product that nobody uses. Say which of
   the two you're claiming.
4. **Watch for a deploy.** A metric that changes shape on a single day is usually a tracking change,
   not a behaviour change.

## Reporting

Give the operator the query you ran, not just its result — project, range, segment, and the event
names. A number they cannot reproduce is a number they cannot act on.

Ranges beat points: "signup→activation is 34%, up from 31% four weeks ago" is useful; "34%" alone is
not. And when the sample is small enough that the swing could be noise, say so rather than letting a
confident sentence imply otherwise.