Integration · Research and analyze

Mixpanel and Meteor AI agents

Connect Mixpanel to a Met: query funnels, retention and reports, review dashboards and cohorts for your product with the official MCP.

Book a demo See every integration

How does Mixpanel connect to Meteor?

With the Mixpanel ready connector, your Met queries your Mixpanel projects with the permissions of the account the admin authorizes. It runs insights, funnel, flow and retention queries, reads saved reports and dashboards, explores events and properties, and reviews data quality issues, cohorts, experiments and feature flags. It also creates and edits dashboards, creates cohorts and edits your event descriptions, if the admin leaves those actions on. Deleting a dashboard or a tag starts turned off. On new accounts the MCP comes enabled; on the rest an organization admin enables it.

What it automates

What a Meteor Met does with Mixpanel

Answer how the funnel is doing

You ask the Met how many users reached checkout this week. The Met checks the query schema, runs the funnel and replies with the conversion of each step.

Read a saved report

If your team already has reports and dashboards in Mixpanel, the Met finds them, brings them with their results and summarizes what they show.

Review data quality

The Met lists the data quality issues of an event or a property, so your team fixes tracking before making decisions with those numbers.

Tidy up the event dictionary

If the admin leaves editing on, the Met adds descriptions and tags to your events and properties in Lexicon, so the whole team understands what each one measures.

28 tools

Everything your Met can ask Mixpanel for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`get_projects`	Lists your Mixpanel projects and workspaces.
`get_business_context`	Returns the project's business context, vocabulary and query instructions.
`get_events`	Searches and lists a project's events, with their metadata if requested.
`list_properties`	Lists and searches event or user properties in a project.
`get_property_values`	Returns the values a property takes.
`search_entities`	Searches across dashboards, reports, experiments, feature flags and more.
`get_query_schema`	Returns the full schema to build a query.
`run_query`	Runs insights, funnel, flow and retention queries.
`get_report`	Returns a saved report, with its results if requested.
`list_dashboards`	Lists a project's dashboards.
`get_dashboard`	Returns a dashboard's metadata, text cards and reports.
`create_dashboard`	Creates a new dashboard with text cards and reports.
`update_dashboard`	Changes a dashboard's metadata, rows and layout.
`delete_dashboard`	Deletes a dashboard. Starts turned off.
`get_issues`	Returns data quality issues filtered by event, property, type or date.
`edit_event`	Changes an event's description, display name, tags or visibility.
`edit_property`	Changes a property's description, display name, hidden status or personal data classification.
`create_tag`	Creates a new tag in Lexicon.
`delete_tag`	Removes a tag from the project. Starts turned off.
`list_cohorts`	Lists the project's cohorts.
`get_cohort`	Returns a cohort's metadata and definition by ID or name.
`create_cohort`	Creates a new cohort.
`list_metrics`	Lists the project's saved metrics.
`get_metric`	Returns the full definition of a saved metric.
`get_user_replays_data`	Analyzes a user's session replays together with their events.
`list_experiments`	Lists and searches a project's experiments. In beta.
`get_experiment`	Returns an experiment's details, configuration and results. In beta.
`get_feature_flag`	Returns a feature flag's details and rules. In beta.

The limits

What the Mixpanel integration does NOT do

We would rather say it here than have you find out during rollout.

It does not filter by cohort in queries. Mixpanel documents that Run-Query cannot filter or break down results by cohort.
It does not use the Europe or India regions. The connector points to Mixpanel's US server; EU and IN accounts use other servers.
It does not delete unless you decide so. Deleting dashboards and tags starts turned off, and the admin decides in Connections which write actions stay on.
It does not see more than you do. Each person signs in with their Mixpanel credentials and the Met only sees the projects that account can access.
It does not pay your Mixpanel plan. Free plans can have Query API limits; Meteor does not resell the service.

Before you start

What you need to connect Mixpanel

1

MCP enabled in your Mixpanel organization

On free and Growth accounts created from August 1, 2026 it comes enabled. On the rest, an organization admin enables it in Settings, Org, Overview.
2

Connect it in Met

In Met, open Connections → Mixpanel → Connect. A Mixpanel window opens so you sign in and authorize Met.
3

Decide which actions stay on

The workspace admin chooses in Connections which actions stay on. Deleting dashboards and tags starts turned off.

Frequently asked questions

Questions about Mixpanel and Meteor

Yes. Mixpanel records changes made through MCP in the same audit log as changes made in its interface, under the connected account.

Yes, if dashboard creation is on. The Met builds the dashboard with the reports and text cards, and shares the result with you.

Because the connected account has no access to that project, or because your organization is in the EU or IN region and this connector uses the US server.

You do, with your Mixpanel account and plan. Met does not charge for the queries your Met makes to Mixpanel.

Step by step