What does Mixpanel Automation via Rube MCP do?

It connects AI assistants to Mixpanel's product analytics platform through Composio's toolkit to automate event data aggregation, segmentation queries, funnel analysis, user profile management, and cohort operations without manual API integration.

What can't this skill do?

It cannot create new funnels or cohorts (these must be created in Mixpanel UI first; the API only queries existing ones), and it should not be used for very large date ranges with segmentation as responses can become extremely large and may time out.

What setup is required to use this skill?

You need to verify Rube MCP availability, call RUBE_MANAGE_CONNECTIONS with toolkit 'mixpanel' to establish an active connection, and add 'https://rube.app/mcp' as an MCP server in your client configuration—no API keys are needed.

What date format does this skill require?

All dates must be in 'YYYY-MM-DD' format, and event names and property names are case-sensitive.

How do I filter events using this skill?

Use Mixpanel expression syntax with the `properties["property_name"]` format, such as `properties["country"] == "US"` for equality, `properties["age"] > 25` for comparison, or combine conditions with `and` for boolean logic.

Skill

Automate Mixpanel Data Analysis with Rube MCP

Name: Mixpanel Automation via Rube MCP
Availability: OnlineOnly
Author: Antigravity

Automates Mixpanel analytics queries - aggregation, segmentation, funnels, cohorts - via Composio's Rube MCP toolkit.

Get skill

Works with mixpanelrube

Antigravity

Own this? Claim it

Spark score

out of 100

Updated last month

Version 13.1.0

Models

universal

Add to Favorites

Why it matters

Leverage Rube MCP to automate complex Mixpanel data analysis, including event aggregation, segmentation, funnel analysis, and user profile management, directly within your workflows.

Outcomes

What it gets done

Aggregate event counts and trends over specified date ranges.

Run detailed segmentation queries by breaking down events by properties.

Analyze conversion funnels to identify drop-off points.

Query and update user profiles and manage cohorts.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-mixpanel-automation | bash

Overview

Mixpanel Automation via Rube MCP

Automates Mixpanel product-analytics workflows - event aggregation, segmentation, funnel analysis, user-profile queries and batch updates, cohort listing, and custom JQL or insight queries - through Composio's Mixpanel toolkit via Rube MCP. Use it once Rube MCP is connected and Mixpanel authentication is ACTIVE, for querying or automating Mixpanel analytics without hand-writing API calls.

What it does

Automates Mixpanel product-analytics workflows through Composio's Mixpanel toolkit via Rube MCP: aggregating event counts and trends (MIXPANEL_AGGREGATE_EVENT_COUNTS), running segmentation queries broken down by event properties (MIXPANEL_QUERY_SEGMENTATION), analyzing conversion funnels and drop-off points (MIXPANEL_LIST_FUNNELS plus MIXPANEL_QUERY_FUNNEL), querying and batch-updating user profiles (MIXPANEL_QUERY_PROFILES plus MIXPANEL_PROFILE_BATCH_UPDATE), listing saved cohorts (MIXPANEL_COHORTS_LIST), and running custom JQL or saved insight queries (MIXPANEL_JQL_QUERY, MIXPANEL_QUERY_INSIGHT). Each workflow documents its required tool sequence, key parameters (event, from_date/to_date, unit, where filter expressions), and known pitfalls - date formats must be YYYY-MM-DD, event and property names are case-sensitive, funnels must already exist in the Mixpanel UI, and large segmentation queries can time out or return capped results.

When to use - and when NOT to

Use it once Rube MCP is connected and a Mixpanel connection is ACTIVE, for querying or automating Mixpanel analytics - event counts, segmentation, funnels, profiles, cohorts, or custom JQL - without hand-writing Mixpanel API calls.

Not usable before setup: it requires RUBE_SEARCH_TOOLS to resolve current tool schemas and RUBE_MANAGE_CONNECTIONS to establish an ACTIVE Mixpanel connection first; funnels and cohorts must already be created in the Mixpanel UI since the API only queries existing ones.

Inputs and outputs

Input: a natural-language analytics request resolved into a Mixpanel tool call, with parameters like event name(s), date range, time granularity, and a Mixpanel expression-syntax filter (e.g. properties["country"] == "US"). Output: aggregated event counts, segmented breakdowns, funnel conversion data, profile query results (paginated via session_id), cohort lists, or JQL/insight query results - typically nested under a data key, with numeric values sometimes returned as strings. Filter expressions follow Mixpanel's own syntax - equality (properties["country"] == "US"), numeric comparison, boolean checks, substring in tests, and AND/OR combinations - and pagination differs by query type: event queries page by adjusting date ranges, profile queries use a page number with a session_id for consistent results, and funnel/cohort lists return complete results without pagination.

Integrations

Runs through Composio's mixpanel toolkit over Rube MCP (https://rube.app/mcp, no API keys needed beyond adding the endpoint), which handles Mixpanel authentication via a connection link. Also documents ID-resolution helpers (project name to project ID via MIXPANEL_GET_ALL_PROJECTS, funnel name to funnel ID via MIXPANEL_LIST_FUNNELS) and Mixpanel's per-project rate limits.

Who it's for

Teams and agents that need to query or automate Mixpanel product analytics - event trends, funnels, cohorts, user profiles - through an MCP-connected workflow rather than the Mixpanel UI or raw API calls.

FAQ

Common questions

Discussion