What your AI apps can do with Mixpanel
- Run segmentation and funnel queries
- Review reports and dashboards
Mixpanel MCP tools
64 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.
| Tool | What it does |
|---|---|
Run-Query | Runs insights, funnel, flow and retention queries |
Get-Query-Schema | Returns the JSON schema used to build queries |
Get-Report | Gets a saved report, optionally with results |
Display-Query | Shows an interactive chart for a query that has already run |
Create-Dashboard | Creates a dashboard with text cards and reports |
List-Dashboards | Lists dashboards in a project |
Get-Dashboard | Gets a dashboard's metadata, text cards and reports |
Update-Dashboard | Updates a dashboard's metadata, rows and layout |
Duplicate-Dashboard | Duplicates an existing dashboard |
Delete-Dashboard | Deletes a dashboard |
Get-Business-Context | Gets org and project business context and query guidance |
Get-Projects | Lists your projects and workspaces |
List-Organizations | Lists the organizations you belong to |
Get-Events | Browses or searches events, optionally with full metadata |
List-Properties | Lists or searches event and user properties |
Get-Property-Values | Gets the values of a property |
Search-Entities | Searches dashboards, reports, experiments, feature flags and more |
Get-Issues | Gets data quality issues filtered by event, property, type or date |
Get-Lexicon-URL | Gets a direct Lexicon link for an event or property |
Edit-Event | Edits an event's description, display name, tags or visibility |
Edit-Property | Edits a property's description, display name, hidden status or PII flag |
Bulk-Edit-Events | Edits up to 50 events at once |
Bulk-Edit-Properties | Edits up to 50 properties at once |
Create-Tag | Creates a Lexicon tag |
Rename-Tag | Renames a tag everywhere it is applied |
Delete-Tag | Deletes a tag from the project |
Dismiss-Issues | Dismisses data quality issues in bulk |
Update-Business-Context | Updates project or org business context |
Find-Duplicate-Groups | Finds duplicate or near-duplicate event and property names |
Dismiss-Duplicate-Group | Dismisses a suggested duplicate group |
Merge-Group | Merges a duplicate group into a single entity |
Create-Custom-Property | Creates a custom property |
Get-Custom-Property | Gets a custom property's definition and details |
Update-Custom-Property | Updates a custom property's definition |
Create-Cohort | Creates a cohort |
Get-Cohort | Gets a cohort's metadata and definition by ID or name |
Update-Cohort | Updates an existing cohort |
Delete-Cohort | Deletes a cohort |
List-Cohorts | Lists cohorts in a project |
Describe-Cohort-Schema | Describes how cohort definitions are structured |
Create-Lookup-Table | Creates a lookup table |
Get-Lookup-Table | Gets a lookup table's schema, row count and row preview |
Update-Lookup-Table | Updates an existing lookup table |
Create-Metric | Creates a reusable behavior or formula metric for experiments |
Get-Metric | Gets a saved metric's full definition |
List-Metrics | Lists saved metrics in a project |
Update-Metric | Updates a saved metric's name, definition or description |
Get-User-Replays-Data | Analyzes a user's session replays together with their events |
List-Experiments | Lists or searches experiments |
Get-Experiment | Gets an experiment's details, configuration and results |
Create-Experiment | Creates an experiment |
Update-Experiment | Updates an experiment's configuration or lifecycle state |
Get-Experiment-Setup-Guidance | Gets best practices for designing experiments |
Get-Experiment-Results-Interpretation-Guidance | Gets best practices for interpreting experiment results |
Explain-Experiment-Health-Check | Explains why an experiment health check is firing |
Run-Experiment-Pre-Launch-Checks | Checks a draft experiment's configuration before launch |
Search-Prior-Experiments | Searches for earlier experiments on the same surface |
List-Feature-Flags | Lists or searches feature flags |
Get-Feature-Flag | Gets a feature flag's details and targeting rules |
Create-Feature-Flag | Creates a feature flag |
Update-Feature-Flag | Updates a feature flag's configuration or targeting |
Get-Feature-Flag-Setup-Guidance | Gets best practices for creating and configuring flags |
Get-Feature-Flag-Lifecycle-Guidance | Gets best practices for flag rollout, kill switches and cleanup |
Get-Audit-Log | Queries the organization's change history (beta, admins only) |
Suggested access for each AI app
The documentation this list comes from doesn't mark Mixpanel's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.
Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.
Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.
Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.
Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Mixpanel connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.
How it works with Toolstile
- Connect once. Add Mixpanel to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
- Choose access per app. Give Claude Code every Mixpanel tool, give Cursor only the read tools, or keep Mixpanel away from an app entirely.
- Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
- Review activity. See which app called which tool and when, so you can tighten access with evidence.
Add the Mixpanel MCP server to an AI app
Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:
claude mcp add --transport http toolstile 'https://toolstile.com/mcp'Then connect Mixpanel in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.
To connect directly instead, add the Mixpanel endpoint to each app separately. In Claude Code:
claude mcp add --transport http mixpanel 'https://mcp.mixpanel.com/mcp'In Cursor's mcp.json:
{
"mcpServers": {
"mixpanel": {
"url": "https://mcp.mixpanel.com/mcp"
}
}
}Some servers accept only clients they have approved, or need a token header. Check the Mixpanel MCP documentation for what your client needs.
Before you connect
A Mixpanel account. Sign-in uses your Mixpanel permissions.
Server details
| Detail | Value |
|---|---|
| Publisher | Mixpanel |
| Endpoint | https://mcp.mixpanel.com/mcp |
| Authentication | Browser sign-in |
| Categories | Marketing & research, Data & infrastructure |
| Tool list | 64 tools, observed 29 October 2026 (docs) |