A Mixpanel MCP that can query everything and delete nothing
Connect one service account and segmentation, funnels, retention, saved Insights reports, user profiles, JQL, raw event export, and server-side event import become workflow steps for visual automations and AI agents. All 23 nodes are reads or additive writes: nothing in this connector can delete or damage analytics data.
What the Mixpanel MCP connector does
The Mixpanel connector for Mattering Automations is 23 nodes across Mixpanel's server-side APIs: event counts and segmentation with sum and average variants, property-value breakdowns, saved funnels with per-step conversion data, retention, saved Insights reports, user profile and cohort queries, JQL scripts, schema discovery (event names, today's top events, top properties, property values, and the Lexicon data dictionary), chart annotations, raw event export, and event import for server-side tracking.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer how signups trended this week, where the activation funnel leaks, and which cohort retained best, without anyone opening the Mixpanel dashboard.
Because Mattering is a work platform rather than middleware, analytics reads land somewhere useful by default: a weekly segmentation digest can arrive as a report task in Mattering Productivity, a funnel step whose conversion drops can open an investigation task, and query results can update records in a Mattering database, all on one canvas next to the rest of the work.
The safety posture is unusual and worth stating plainly: 20 of the 23 nodes are pure reads, and the three writes create a chart annotation, import events, or set profile properties. Nothing in the catalog deletes or destroys anything, so no workflow built from these nodes can damage the analytics data your team depends on.
One connection, three surfaces
- Visual automations. Drag Mixpanel nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Mixpanel node, ready to drop on the canvas
23 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 20
Mixpanel: Average a Numeric Expression
Average a numeric property expression across one event per time bucket, e.g. average order value per day. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Export Raw Events
Download raw event records (every tracked event with all its properties) for a date range from Mixpanel's export cluster. WARNING: unfiltered exports can be enormous; always set limit (server cap 100,000 events) and keep date ranges tight, because the full result is stored in the execution record. The response is newline-delimited JSON, which this node parses into an events array for downstream steps. Export budget: 60 queries per hour, 3 per second.
Mixpanel: Get Event Counts Over Time
Get counts for one or MORE events bucketed over time in a single call: the simplest multi-event trend read (segmentation handles one event with property breakdowns). Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Get Today's Top Events
Get today's top events by volume, each with its count and the percent change from yesterday. A quick daily pulse read for digest or alerting automations. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Annotations
List the chart annotations on a project (release markers, campaign launches, incidents), optionally windowed by date. Each annotation carries its id, timestamp, description, author, and tags.
Mixpanel: List Cohorts
List the project's saved cohorts with id, name, description, current member count, and visibility. Feed a cohort id into the Query Profiles node's filter_by_cohort to pull the members. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Event Names
List the names of events tracked in the project over the last 31 days, for discovering what can be queried. Returns a plain array of event name strings. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Lexicon Schemas
Read the project's Lexicon data dictionary: every uploaded schema for events and profile properties, with names, entity types, descriptions, and property definitions. Useful for schema discovery before building queries.
Mixpanel: List Saved Funnels
List the project's saved funnels with their funnel_id and name, for feeding the funnel query node. Note: Mixpanel keeps the Funnels endpoints in maintenance mode and recommends the Insights query node for new work; this still works and is the only way to enumerate funnel IDs. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Top Properties of an Event
List the most common property names on one event, with a count for each: the schema-discovery step before segmenting on a property. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: List Top Values of an Event Property
List the most common values of one property on one event, as a plain array of strings. Pairs with the top-properties node to map an event's schema before querying. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query Retention
Get cohort retention data: for each cohort start date, the size of the cohort and how many returned in each subsequent time bucket. Supports first-time (birth) and recurring (compounded) retention. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query User Profiles
Query user (or group) profiles: fetch by distinct_id, filter with a where expression, or pull a cohort's members via filter_by_cohort. Pages of up to 1,000 profiles; to get the next page, send back the returned session_id and increment page, keeping the same filters. Profile data is personal data and persists in execution records; select only the properties you need with output_properties. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query a Saved Funnel
Get per-step conversion data for a saved funnel over a date range: step counts, step and overall conversion ratios, and average times between steps. Note: maintenance mode; Mixpanel recommends building a funnel in Insights and using the Insights query node for new work. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Query a Saved Insights Report
Pull the computed data of a saved Insights report by its bookmark ID (the number in the report URL). This is Mixpanel's recommended programmatic path for report data, including funnel reports built in the UI. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Run a JQL Query
Run a custom JQL script (Mixpanel's JavaScript query language) against the project's events and profiles. The script executes inside Mixpanel's sandbox, can only READ analytics data, and cannot make network requests; results come back as a JSON array. Limits: 2 minutes of runtime, 5 GB scanned, 2 GB output. Note: JQL is in maintenance mode; prefer the typed query nodes when one fits. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Segment an Event
The workhorse analytics read: count one event over time, optionally filtered with a where expression and broken down by a property expression (on). Returns a date series per segment value. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Segment an Event by Property Values
Count one event over time broken down by the values of one named property, optionally restricted to specific values. The simpler cousin of the segmentation node when you have a plain property name rather than an expression. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Sum a Numeric Expression
Sum a numeric property expression across one event per time bucket, e.g. total revenue per day from a purchase event's amount property. Query API budget: 60 queries per hour, at most 5 concurrent, shared across all query nodes on this connector.
Mixpanel: Verify Credential (List Accessible Projects)
Confirm the service account credential works and see which organization, projects, and workspaces it can reach. Takes no parameters and does not count against the query rate limit, so it doubles as the credential health check and as the way to look up project IDs for the other nodes.
Action nodes 3
Mixpanel: Create Annotation
Add a chart annotation to a project, e.g. mark a deploy, a campaign start, or an incident so it shows on every Mixpanel chart at that timestamp. Requires the service account to hold an Analyst role or higher on the project. Reversible: an annotation can be deleted in the Mixpanel UI.
Mixpanel: Import Events
Send events INTO Mixpanel from an automation (server-side tracking) using the same service account credential as the query nodes. Each event needs an event name plus properties with time, distinct_id, and a $insert_id for deduplication. Up to 2,000 events per call. Note: imported events cannot be deleted through this connector, so point test runs at a throwaway project or a clearly named test event.
Mixpanel: Set User Profile Properties
Set (create or overwrite) properties on one user profile. NOTE ON CREDENTIALS: Mixpanel's profile ingestion authenticates with the project TOKEN (a public identifier from Project Settings, then Access Keys), not the service account, so this node has its own project_token field. Careful: $set OVERWRITES an existing value for each property it names; properties not named are left untouched.
Connecting Mixpanel takes one credential
Mixpanel issues service accounts from Organization Settings under Service Accounts. A service account is a username and secret pair sent as HTTP Basic auth on every request; the secret is shown once at creation, and an optional expiration date can be set. Service accounts belong to the organization with per-project roles, which is why every query node also asks for a project_id.
In Mixpanel, open Organization Settings, go to Service Accounts, and create a service account with roles on the projects you want to automate. Copy the username and the secret; the secret is shown only once.
In Mattering Automations, open Connectors, click Add Connector, choose Mixpanel, and create a credential with the service account username as the username and the secret as the password.
Click Test Connection. Mattering calls Mixpanel's me endpoint and confirms the credential authenticates, without spending any query budget.
All 23 Mixpanel nodes appear in the canvas palette. Run Mixpanel: Verify Credential (List Accessible Projects) first: it lists the organization, projects, and workspaces the account can reach, and its project ids are what every query node needs.
Common uses for the Mixpanel MCP
Trends and segmentation an agent can read
Mixpanel: Segment an Event counts one event over time with where filters and property breakdowns, Mixpanel: Segment an Event by Property Values does the same with a plain property name, and Mixpanel: Get Event Counts Over Time trends several events in a single call. Mixpanel: Sum a Numeric Expression and Mixpanel: Average a Numeric Expression turn a purchase event's amount property into revenue per day or average order value.
Schema discovery before anyone queries
Mixpanel: List Event Names returns what the project has tracked over the last 31 days, Mixpanel: Get Today's Top Events gives a daily pulse with percent change from yesterday, and Mixpanel: List Top Properties of an Event with Mixpanel: List Top Values of an Event Property map an event's schema before segmenting on it. Mixpanel: List Lexicon Schemas reads the project's data dictionary, so an assistant can learn what fields mean before building a query.
Funnels, retention, and saved reports
Mixpanel: Query a Saved Insights Report pulls the computed data of any saved report by its bookmark id, which is Mixpanel's recommended programmatic path, including for funnel reports built in the UI. Mixpanel: List Saved Funnels and Mixpanel: Query a Saved Funnel return per-step conversion for legacy saved funnels, and Mixpanel: Query Retention reports how each cohort of users comes back over time.
Profiles and cohorts, carefully
Mixpanel: List Cohorts enumerates saved cohorts with member counts, and Mixpanel: Query User Profiles pulls profiles by distinct_id, by a where expression, or by cohort membership, in pages of up to 1,000. Profile reads are personal data that persist in execution records, so the node pushes you to select only the properties you need.
Deploy markers on every chart
Mixpanel: Create Annotation stamps a deploy, campaign launch, or incident onto the project timeline so it shows on every Mixpanel chart at that timestamp, and Mixpanel: List Annotations reads the markers back. Wire the create node into the end of a release workflow and the analytics team sees exactly when each version shipped, right on the charts they already watch.
Raw events out, events in, and the JQL escape hatch
Mixpanel: Export Raw Events downloads the underlying event records for a date range, parsed from Mixpanel's newline-delimited JSON into a normal events array and capped at 100,000 events per call. Mixpanel: Import Events sends events the other way for server-side tracking, on the same service account credential. When no typed node fits, Mixpanel: Run a JQL Query runs a read-only script inside Mixpanel's sandbox, with no network access and results returned as a JSON array.
Example: A weekly product digest that lands as a task, with funnel drop-offs opening their own
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule fires Monday morning.
Mixpanel: Segment an Event counts the week's signup events broken down by plan.
Mixpanel: Sum a Numeric Expression totals the amount property on purchase events for the week's revenue.
Mixpanel: Query a Saved Insights Report pulls the activation funnel the team already built in the Mixpanel UI, by its bookmark id.
A condition compares each funnel step's conversion to the prior week and opens an investigation task in Mattering Productivity for any step that dropped.
The digest itself, signups by plan, revenue, and the funnel summary, lands as a report task in Mattering Productivity for the team to review at Monday standup.
Mixpanel MCP questions, answered
What Mixpanel operations are supported?
23 nodes: 20 queries and 3 actions. The queries cover event counts over time, segmentation with where and on expressions plus sum and average variants, property-value breakdowns, saved funnels and per-step funnel data, retention, saved Insights reports by bookmark id, user profiles and cohorts, JQL scripts, schema discovery (event names, today's top events, top properties and values, Lexicon schemas), annotations, raw event export, and a credential verification read. The actions create chart annotations, import events, and set user profile properties. Deliberately not shipped: the client-side track endpoint (the import node covers server-side sending on the connector's own credential), profile mutators beyond set, group profile ingestion, annotation and Lexicon writes beyond those listed, service account management, the Warehouse Connectors API, and Mixpanel's GDPR deletion APIs.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. Because 20 of the 23 nodes are pure reads, this is an unusually safe connector to hand an agent.
Can this connector damage my Mixpanel data?
No. There are zero destructive nodes: 20 of the 23 are pure queries, and the three writes only add or update. Mixpanel: Create Annotation adds a chart marker you can delete in the Mixpanel UI, Mixpanel: Import Events adds events, and Mixpanel: Set User Profile Properties updates a profile. Two honest caveats within that: imported events cannot be deleted through this connector (deletion is Mixpanel's separate GDPR tooling), so point test runs at a throwaway project or a clearly named test event, and the profile node overwrites the values of the properties it names.
Why does every query node need a project_id?
Because the credential cannot imply one. Mixpanel service accounts belong to the organization, not to a project, with per-project roles, so the API requires each query to say which project it targets. Mixpanel: Verify Credential (List Accessible Projects) doubles as the lookup: it lists every project the account can reach with its id, and the same number is in Project Settings and in the project URL. Projects using Data Views can also pass an optional workspace_id.
Why does the profile node ask for a project token instead of using the connector credential?
Because Mixpanel's profile ingestion endpoint has no service account variant: it authenticates with the project token, a public identifier from Project Settings under Access Keys, not a secret. Mixpanel: Set User Profile Properties is the one node in the connector with its own project_token field for exactly this reason. The connector credential stays the service account, full stop; the token is per-node configuration on the single node whose API demands it.
What is the story with funnels and JQL?
Both ship, with Mixpanel's own caveat stated honestly: Mixpanel keeps the Funnels endpoints and JQL in maintenance mode and steers new work to Insights. Mixpanel: List Saved Funnels and Mixpanel: Query a Saved Funnel are still the only programmatic path to legacy saved-funnel step data, so they are included. For new work, build the funnel in the Mixpanel UI and pull it with Mixpanel: Query a Saved Insights Report by bookmark id. Mixpanel: Run a JQL Query remains useful when no typed node fits: the script runs read-only inside Mixpanel's sandbox with no network access.
Can a Mixpanel event trigger a workflow?
Not in this connector: there is no inbound Mixpanel trigger. The honest pattern is a scheduled sweep: run a query node such as Mixpanel: Segment an Event or Mixpanel: Get Today's Top Events on a schedule, compare against a threshold or the prior period, and route what changed into tasks or messages. Mind the shared budget when scheduling: the Query API allows 60 queries per hour with at most 5 concurrent, shared across all query nodes on the credential.
Does this work with EU or India data residency?
Not in this version. Mixpanel operates separate EU and India residency hosts, and this connector deliberately speaks only to the US hosts, so a project stored in the EU or India will fail to authenticate or return empty data. If your projects live on US residency, which is Mixpanel's default, everything works as described. Regional host support is a candidate for a future version.
Put Mixpanel to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Mixpanel is a product of its respective owner; Mattering is an independent platform.