How to integrate Mixpanel MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Mixpanel logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Mixpanel to Mastra AI using the Composio tool router. By the end, you'll have a working Mixpanel agent that can show daily active users for last month, list top events by user engagement, analyze conversion funnel for signup flow through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Mixpanel account through Composio's Mixpanel MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Mixpanel with

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Mixpanel tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Mixpanel tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Mixpanel agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Mixpanel MCP server, and what's possible with it?

The Mixpanel MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mixpanel account. It provides structured and secure access to your product analytics data, so your agent can perform actions like retrieving event metrics, analyzing cohorts, exploring funnels, and running custom queries on your behalf.

  • Event property and trend analysis: Ask your agent to fetch unique, total, or average values for specific events and properties over time to spot trends and measure engagement.
  • Cohort and funnel exploration: Have your agent pull lists of saved cohorts or funnels, or retrieve detailed funnel performance data to understand user journeys.
  • User activity and frequency reporting: Direct your agent to analyze how frequently users perform key events or to get event activity feeds for individual profiles.
  • Custom JQL query execution: Run advanced, custom JavaScript queries through your agent for deep, flexible analytics tailored to your business questions.
  • Project and configuration management: Let your agent list all Mixpanel projects under your account, giving you quick access to metadata and configuration details.

Supported Tools & Triggers

Tools
Add Unique Values to Profile List PropertyTool to add unique values to list properties on user profiles in Mixpanel using the $union operation.
Get Aggregated Event Property ValuesGet unique, total, or average data for a single event and property over days, weeks, or months.
Get Aggregate EventsGet aggregate event counts over time.
List Saved CohortsTool to list all saved cohorts in a Mixpanel project.
Create Annotation TagTool to create a new annotation tag in Mixpanel using the provided name.
Create IdentityTool to create an identity mapping in Mixpanel by linking an anonymous ID with an identified user ID.
Create Service AccountTool to create a new service account for your organization and optionally add it to projects.
Delete GroupTool to permanently delete a group profile from Mixpanel Group Analytics.
Delete ProfileTool to permanently delete a user profile from Mixpanel, along with all of its properties.
Delete Multiple Profiles (Batch)Tool to permanently delete multiple user profiles from Mixpanel in a single batch request.
Delete Profile PropertyTool to permanently delete properties from a Mixpanel user profile using the $unset operation.
Get All ProjectsGet all projects associated with the authenticated Mixpanel account.
Get Annotation TagsTool to get all annotation tags from a Mixpanel project.
Batch Update Group ProfilesTool to send a batch of group profile updates to Mixpanel.
Delete Group PropertiesTool to delete specific properties from a Mixpanel group profile.
Create Identity AliasTool to create an alias mapping between two distinct IDs in Mixpanel.
Execute JQL QueryExecute a custom JQL (JavaScript Query Language) query against Mixpanel's Query API.
List Saved FunnelsGet the names and funnel_ids of your funnels.
List Service AccountsTool to list all service accounts for an organization.
Append to Profile List PropertyTool to append values to list properties on user profiles in Mixpanel.
Update Multiple Profiles (Batch)Tool to update multiple user profiles in Mixpanel in a single batch request.
Get Profile Event ActivityGet event activity feed for specified users from Mixpanel Query API.
Increment Profile Numerical PropertyTool to increment or decrement numerical properties on user profiles in Mixpanel.
Remove from Profile List PropertyTool to remove values from list properties on user profiles in Mixpanel.
Set Profile PropertiesTool to set user profile properties in Mixpanel using the $set operation.
Query Frequency ReportGet data about how frequently users are performing events.
Query Saved FunnelGet data for a funnel.
Query Saved InsightGet data from your Insights reports.
Query Numeric Average ReportAverages an expression for events per unit time.
Query Numeric Sum ReportSums an expression for events per unit time.
Query ProfilesQuery user or group profile data from Mixpanel.
Query Retention ReportQuery cohort analysis showing user retention patterns over time.
Query Segmentation ReportGet data for an event, segmented and filtered by properties with daily/time-series breakdown.
Query Top EventsGet the top events for today, with their counts and the normalized percent change from yesterday.
Remove from Group List PropertyTool to remove values from list properties on group profiles in Mixpanel.
Remove from Profile List PropertyTool to remove values from list properties on user profiles in Mixpanel using the $remove operation.
Numeric Bucket Segmentation QueryTool to get event data numerically bucketed by property values.
Set Group Property OnceTool to set properties on a Mixpanel group profile only if they don't already exist.
Set Profile Property OnceTool to set user profile properties in Mixpanel using the $set_once operation.
Get Top Event PropertiesGet the top property names for an event.
Get Top Event Property ValuesTool to get the top values for a property ordered by frequency.
Get Top EventsGet a list of the most common events over the last 31 days.
Union to Group List PropertyTool to add unique values to list properties on group profiles in Mixpanel.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Mixpanel through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Mixpanel

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["mixpanel"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Mixpanel MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "mixpanel" for Mixpanel access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Mixpanel toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "mixpanel-mastra-agent",
    instructions: "You are an AI agent with Mixpanel tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        mixpanel: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Mixpanel toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Mixpanel and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["mixpanel"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      mixpanel: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "mixpanel-mastra-agent",
    instructions: "You are an AI agent with Mixpanel tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { mixpanel: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Mixpanel through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Mixpanel MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Mixpanel MCP?

With a standalone Mixpanel MCP server, the agents and LLMs can only access a fixed set of Mixpanel tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mixpanel and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Mixpanel tools.

Can I manage the permissions and scopes for Mixpanel while using Tool Router?

Yes, absolutely. You can configure which Mixpanel scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Mixpanel data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.