mixpanel
Server Details
Query Mixpanel events, funnels, retention, segmentation and insights (JQL).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
7 toolsmixpanel_jqlRun a JQL queryRead-onlyInspect
Run a custom JQL (JavaScript Query Language) script for arbitrary analysis. Power-user escape hatch. Script must define main(). Query API: POST /jql. (Upstream maintenance mode; 2-min timeout, 5GB/query limit.)
| Name | Required | Description | Default |
|---|---|---|---|
| params | No | Optional JSON string exposed to the script as the `params` global. | |
| script | Yes | JQL script defining function main(){ ... } that returns rows. |
mixpanel_list_funnelsList saved funnelsRead-onlyInspect
Get the funnel_id and name of every saved funnel in the project. Query API: GET /funnels/list.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
mixpanel_query_funnelQuery a saved funnelRead-onlyInspect
Get conversion data for a saved funnel (use mixpanel_list_funnels to find funnel_id). Query API: GET /funnels.
| Name | Required | Description | Default |
|---|---|---|---|
| unit | No | Bucketing unit. | |
| limit | No | Limit on segmentation breakdown. | |
| length | No | Conversion window length. | |
| to_date | Yes | End date yyyy-mm-dd (inclusive). | |
| interval | No | Number of days per bucket. | |
| from_date | Yes | Start date yyyy-mm-dd (inclusive). | |
| funnel_id | Yes | Saved funnel id (from mixpanel_list_funnels). | |
| length_unit | No | Unit for `length`. |
mixpanel_query_insightsQuery a saved Insights reportRead-onlyInspect
Fetch the computed data behind a saved Insights report by bookmark_id (the report id in the board URL). Mixpanel's recommended, non-deprecated path for programmatic reporting. Query API: GET /insights.
| Name | Required | Description | Default |
|---|---|---|---|
| bookmark_id | Yes | Insights report id (bookmark_id) from the report URL. | |
| workspace_id | No | Workspace id, if applicable. |
mixpanel_retentionRetention reportRead-onlyInspect
Cohort retention: of users who did born_event, how many came back and did event over subsequent intervals. Query API: GET /retention.
| Name | Required | Description | Default |
|---|---|---|---|
| unit | No | Interval unit. Default day. | |
| event | No | Returning event to measure. If omitted, any event counts. | |
| where | No | Filter expression applied to the returning event. | |
| to_date | Yes | End date yyyy-mm-dd (inclusive). | |
| interval | No | Units per bucket (<=90 if days). Default 1. | |
| from_date | Yes | Start date yyyy-mm-dd (inclusive). | |
| born_event | No | The defining first event for a birth cohort. Required when retention_type=birth. | |
| born_where | No | Filter expression applied to born_event. | |
| interval_count | No | Number of intervals to report. | |
| retention_type | No | birth = first-time retention (default), compounded = recurring. |
mixpanel_segmentationSegment an eventRead-onlyInspect
Count/segment/filter a single event over a date range. e.g. 'Signed up' by country last week. Params on/where use Mixpanel segmentation expressions like properties["$country_code"]. Query API: GET /segmentation. (Upstream maintenance mode — for saved reports prefer mixpanel_query_insights.)
| Name | Required | Description | Default |
|---|---|---|---|
| on | No | Property expression to segment on, e.g. properties["$city"]. | |
| type | No | general | unique | average. Default general. | |
| unit | No | Bucket size. Default day. | |
| event | Yes | Single event name to analyze (not an array). | |
| limit | No | Top N property values (only if `on` set). Default 60. | |
| where | No | Filter expression, e.g. properties["$os"]=="iOS". | |
| to_date | Yes | End date yyyy-mm-dd (inclusive). | |
| from_date | Yes | Start date yyyy-mm-dd (inclusive). |
mixpanel_top_eventsTop events (today)Read-onlyInspect
List today's top events with counts and % change vs yesterday. Good first call to discover what events a project tracks. Query API: GET /events/top.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | general (totals), unique (per-user), or average. Default general. | |
| limit | No | Max events to return. Default 100. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!