Mixpanel

Apply the same edit to multiple events at once. Provide a list of event_names and one or more fields to update. Supported fields: hidden, verified, dropped, tags, contact_emails, team_contact_names. Maximum 50 events per call.

Apply the same edit to multiple properties at once. Provide a list of property_names, a resource_type ("Event" or "User"), and one or more fields to update. Supported fields: hidden, dropped, sensitive. Maximum 50 properties per call.

Create a Mixpanel dashboard that combines multiple reports and text into a single view. Use when the user asks for a "dashboard," "board", or requests to save several reports grouped together. For a single report request, prefer Run-Query.

Requires query_id(s) from prior Run-Query calls (use skip_results=true to chain multiple queries).

Max 30 rows per dashboard. Each row can contain up to 4 items (text cards or reports).

Row schema: {'$defs': {'ReportContent': {'description': 'Report content for a dashboard row.', 'properties': {'type': {'const': 'report', 'default': 'report', 'title': 'Type', 'type': 'string'}, 'query_id': {'description': 'query_id from Run-Query', 'title': 'Query Id', 'type': 'string'}, 'name': {'maxLength': 255, 'title': 'Name', 'type': 'string'}, 'description': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'title': 'Description'}}, 'required': ['query_id', 'name'], 'title': 'ReportContent', 'type': 'object'}, 'TextContent': {'description': 'Text content for a dashboard cell.', 'properties': {'type': {'const': 'text', 'default': 'text', 'title': 'Type', 'type': 'string'}, 'html_content': {'description': 'HTML content for the text card. Allowed tags: a, blockquote, br, code, em, h1, h2, h3, hr, li, mark, ol, p, s, strong, u, ul. Other tags are stripped. Do not include newlines; Each html element means a new line.', 'maxLength': 2000, 'title': 'Html Content', 'type': 'string'}}, 'required': ['html_content'], 'title': 'TextContent', 'type': 'object'}}, 'description': 'A row to add to a dashboard.', 'properties': {'contents': {'items': {'discriminator': {'mapping': {'report': '#/$defs/ReportContent', 'text': '#/$defs/TextContent'}, 'propertyName': 'type'}, 'oneOf': [{'$ref': '#/$defs/TextContent'}, {'$ref': '#/$defs/ReportContent'}]}, 'maxItems': 4, 'minItems': 1, 'title': 'Contents', 'type': 'array'}}, 'required': ['contents'], 'title': 'DashboardRow', 'type': 'object'} Time filter schema: {'$defs': {'DateRange': {'description': 'Date range specification for dashboard time filter.', 'properties': {'type': {'description': 'Type of date range', 'enum': ['since', 'between', 'in the last'], 'title': 'Type', 'type': 'string'}, 'from': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'description': "Start date (YYYY-MM-DD) for 'since' or 'between'", 'title': 'From'}, 'to': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'description': "End date (YYYY-MM-DD) for 'between'", 'title': 'To'}, 'window': {'anyOf': [{'$ref': '#/$defs/TimeWindow'}, {'type': 'null'}], 'default': None, 'description': "Time window for 'in the last'"}}, 'required': ['type'], 'title': 'DateRange', 'type': 'object'}, 'TimeWindow': {'description': 'Time window for relative date ranges.', 'properties': {'unit': {'description': 'Time unit', 'enum': ['day', 'week', 'month'], 'title': 'Unit', 'type': 'string'}, 'value': {'description': 'Number of units', 'minimum': 1, 'title': 'Value', 'type': 'integer'}}, 'required': ['unit', 'value'], 'title': 'TimeWindow', 'type': 'object'}}, 'description': 'Dashboard time filter.', 'properties': {'dateRange': {'$ref': '#/$defs/DateRange', 'description': 'Date range configuration'}, 'displayText': {'description': "Human-readable display text, e.g. 'Last 30 days'", 'title': 'Displaytext', 'type': 'string'}}, 'required': ['dateRange', 'displayText'], 'title': 'DashboardTimeFilter', 'type': 'object'}

Create a tag for organizing events and properties in Lexicon.

Delete a dashboard. Always confirm with the user before proceeding. Use List-Dashboards or Get-Dashboard to find the dashboard ID.

Delete a tag from a Mixpanel project. This removes the tag from all associated events and properties. Use with caution as this operation cannot be undone.

Dismiss data quality issues matching natural criteria - no need to look up IDs first. Specify what to dismiss using event names, property names, dates, and issue types.

Example: dismiss issues for the 'signup' event from November 15th, or dismiss all type drift issues for the 'user_id' property.

IMPORTANT: If multiple issues match your criteria, you must set dismiss_all_matching=True as a safety measure. To dismiss a single issue, provide enough criteria to uniquely identify it (event + date, or property + date).

Display the interactive chart widget for a previously-run query. Takes a query_id returned by Run-Query and render results in the MCP App visualization widget.

Create a copy of an existing dashboard with all its contents. Optionally override the title and description of the new dashboard.

Use contact_emails or team_contact_names for ownership. Set verified=True to verify/approve events, hidden=True to hide from UI, dropped=True to deprecate.

Set sensitive=True for PII data classification.

Set include_layout=True to get full layout with cell/row IDs (needed for Update-Dashboard). Layout format: [[row_id, [[cell_id, type, extra], ...]], ...].

Get an event's full metadata. Use before editing to see current state.

Get events for a Mixpanel project.

Two lookup modes (mutually exclusive):

• event_names: Look up specific events by exact name. Lightweight server-side filter.
• query: Search/discover events by substring match (case-insensitive). Fetches all events.

include_details: When True, return full event metadata (tags, description, display_name, verified, hidden, dropped) for each event. Set to false if no details are needed, to keep the response compact. tag: Filter to events that have this tag name. verified/hidden/dropped: Filter by metadata status (True or False).

Get all data quality issues for a Mixpanel project. Returns rich context with human-readable descriptions, event/property names, timestamps, and variance details. Filter by event name, property name, issue type, status, date range, or search by description.

Return a Mixpanel Lexicon transformations detail URL for an event or property. Provide either event or property along with project_id.

If workspace_id is omitted, the tool will choose the 'All project data' workspace. Use this when the user wants to change event/property metadata such as display name and description.

Get projects that are accessible to current user. Returns the project's id, name, workspaces and context. Use this and prompt the user to select a project from the available projects.

Get a property's full metadata. Use before editing to see current state.

List property names. resource_type: 'Event' for event properties (set 'event' to scope to one event), 'User' for user properties, or omit for both.

For Event properties, the 'event' parameter is required.

Get the full instructions and JSON schema for building a full Mixpanel query. Call this to learn all available fields and options for the 'report' parameter in Run-Query.

report_type: 'insights', 'funnels', 'flows', or 'retention'.

Retrieve a saved report from a Mixpanel project. Optionally include the report results if it's a queryable report type.

Get session replays information. Provide either a distinct_id (with from_date and to_date) to find all replays for a user, OR a list of specific replay_ids (up to 20) to analyze directly.

Optionally include event_properties (up to 5) to fetch specific property values for each event.

Prefer Search-Entities with entity_types=['dashboard'] instead, it offers more flexibility and efficiency.

Returns a list of all the dashboards in the project. Use query to filter by title (case-insensitive substring match).

Rename an existing tag in a Mixpanel project. The new name must be unique within the project (max 175 characters). This updates all events and properties currently using this tag.

Run a single analytics query and return its results directly. Use this whenever the user requests a chart, a report, a metric, explore a behavior or root cause, or asks to "create a report".

Returns results to chain queries iteratively. Only use skip_results=true when building a dashboard or you won't use the results.

Report types:

• insights: Basic report, supports different chart types, trends, and metric aggregations.
• funnels: Conversion rates between sequential events within a time window. Requires at least 2 steps.
• flows: Most frequent user paths to or from events. Shows steps before/after/between events as a sankey or paths chart.
• retention: User engagement over time. Requires exactly 2 events: an initial action and a retention action.

For very simple insights queries, use this schema as the report parameter: { "name": "string", "metrics": [ { "eventName": "string", "measurement": { "type": "basic", "math": "total | unique" } } ], "chartType": "table | line | bar", "unit": "hour | day | week | month", "dateRange": { "type": "relative", "range": { "unit": "day | week | month", "value": "integer" } } }

For more elaborated queries, with multiple events, filters, breakdowns, formulas or advanced measurements you must call Get-Query-Schema(report_type: 'insights'|'funnels'|'flows'|'retention') first to see the full schema for the report parameter.

Keep responses compact: prefer short date ranges (7-30 days) or coarser granularity (week/month), and avoid combining many breakdowns with fine-grained time series.

Search across all entities in a Mixpanel project: dashboards, reports, cohorts, experiments, feature flags, metric trees, playlists, and heat maps.

query: can be empty to browse by sort order. entity_types: set to include specific entity types. Values: insights, funnels, flows, retention, dashboard, launch-analysis, experiments, feature-flags, metric-trees, playlists, heat-maps, cohort.

• Use Get-Report to fetch full details for insights, funnels, flows, and retention types.
• Use Get-Dashboard to fetch full details for dashboards.

Call Get-Dashboard with include_layout=True first to get cell/row IDs.

• To update a report cell query_id, call Run-Query first.
• To add rows or cells, use any temporary string ID (e.g. "temp-row-1").
• To add cell in a new row, use the row temp id in the cell definition.
• For updates and deletes, use real row and cell ids from Get-Dashboard.

rows: ['<row_id>', 'add'] | ['<row_id>', 'delete'] Content: {type: 'text', html_content: 'string'} | {type: 'report', query_id: 'string', name: 'string', description: 'string'} cells: ['<cell_id>', 'create', 'text' | 'report', {row_id: 'string', ...Content}] | ['<cell_id>', 'update', 'text' | 'report', {...Content}] | ['<cell_id>', 'delete']