Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Mixpanel MCP Server for Claude

Query Mixpanel analytics data from Claude — run insights, funnels, flows, retention analysis, manage dashboards, explore events and properties, run experiments, and analyze session replays — with the official Mixpanel remote MCP server.

by Mixpanel·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • The server is hosted by Mixpanel and authenticated via OAuth — your existing Mixpanel project permissions are automatically applied.
  • The MCP server grants read and write access to your Mixpanel project; it can create and modify dashboards, reports, and feature flags.
  • Treat Service Account credentials as secrets; do not commit them to repositories.

Privacy notes

  • Queries and analytics results (event data, user properties, funnel metrics) are sent through Mixpanel's hosted MCP infrastructure.
  • Session replay summaries and user segment data may surface in Claude's context — treat these as sensitive product analytics.

Prerequisites

  • A Mixpanel account — authenticate via OAuth when prompted on first tool use.
  • EU customers should use `https://mcp-eu.mixpanel.com/mcp`; India customers `https://mcp-in.mixpanel.com/mcp`.
  • Service Account credentials (Beta) are available for headless/CI use.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.mixpanel.com/mcp"]
    }
  }
}

About this resource

Overview

The Mixpanel MCP Server is the official remote Model Context Protocol server from Mixpanel. It gives Claude direct access to your Mixpanel product analytics — run insights, funnels, flows, and retention queries; manage dashboards; discover events and properties; run A/B experiments; and analyze session replays — all through natural language, without opening the Mixpanel dashboard.

The server launched in public beta in April 2026. Authentication is via OAuth (recommended) or Service Account credentials (beta, for headless workflows). Regional endpoints are available for US, EU, and India.

Key capabilities

The server exposes 40+ tools across six categories:

  • Analytics — run insights, funnels, flows, retention, and cohort queries.
  • Dashboards — create, retrieve, and manage boards and reports.
  • Data discovery — browse events, properties, and data quality issues.
  • Data management — edit events and properties, manage tags, dismiss issues.
  • Experiments & feature flags (Beta) — create and configure feature flags, run A/B experiments.
  • Session replays — analyze user behavior alongside event-level data.

How it compares

Server Funnel/retention queries Dashboard management Feature flags Session replays Auth
Mixpanel MCP Yes Yes Yes (Beta) Yes OAuth / Service Account
Amplitude MCP Yes Limited No No API key
PostHog MCP Yes Yes Yes Yes API key
Google Analytics MCP Limited Limited No No OAuth

Mixpanel's MCP is notable for combining analytics queries, dashboard management, feature flags, and session replay access in a single hosted endpoint with OAuth-based access control.

Installation

Claude Code (OAuth — recommended)

claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp

Run /mcp in Claude Code to complete the OAuth flow.

Claude Desktop (OAuth)

{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.mixpanel.com/mcp"]
    }
  }
}

Restart Claude Desktop; you will be prompted to authenticate with your Mixpanel account on first use.

Service Account (headless/CI)

Generate credentials in Mixpanel under Organization Settings → Service Accounts, then encode as base64(username:secret) and add the Authorization: Bearer Basic <base64> header to your MCP client configuration.

Regional endpoints

Region URL
US https://mcp.mixpanel.com/mcp
EU https://mcp-eu.mixpanel.com/mcp
India https://mcp-in.mixpanel.com/mcp

Requirements

  • A Mixpanel account.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • OAuth is preferred; it automatically scopes access to your existing Mixpanel project permissions.
  • Service Account credentials are secrets — store them securely and rotate on exposure.
  • The server can write to dashboards and feature flags; review Claude's proposed changes before confirming in production projects.

Source Verification Notes

Verified on 2026-06-18:

  • Mixpanel's official MCP documentation at docs.mixpanel.com/docs/mcp confirms the US/EU/IN endpoints, OAuth and Service Account authentication, the 40+ tools across six categories, and the Claude Code installation command.
  • Mixpanel's blog announcement confirms the server launched in public beta in April 2026 and describes the natural-language analytics use cases.
  • Claude Code's MCP documentation describes the --transport http installation pattern used above.
#mixpanel#analytics#product-analytics#funnels#retention#feature-flags#experiments

Source citations

Add this badge to your README

Show that Mixpanel MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/mixpanel-mcp-server.svg)](https://heyclau.de/entry/mcp/mixpanel-mcp-server)

How it compares

Mixpanel MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldMixpanel MCP Server for Claude

Query Mixpanel analytics data from Claude — run insights, funnels, flows, retention analysis, manage dashboards, explore events and properties, run experiments, and analyze session replays — with the official Mixpanel remote MCP server.

Open dossier 		GrowthBook MCP Server for Claude

Manage A/B experiments and feature flags in GrowthBook from Claude — list and create experiments, manage feature flags, check experiment results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server.

Open dossier 		LaunchDarkly MCP Server for Claude

Manage LaunchDarkly feature flags, AI configs, environments, and audit logs from Claude — with the official LaunchDarkly Model Context Protocol server backed by the LaunchDarkly REST API.

Open dossier 		ConfigCat MCP Server for Claude

Manage ConfigCat feature flags from Claude — create, update, and delete flags and targeting rules, manage environments, find and clean up stale flags, and audit change history — with the official ConfigCat MCP server and its 52 tools for the full ConfigCat Management API.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorMixpanelGrowthBookLaunchDarklyConfigCat
Added2026-06-182026-06-182026-06-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓The server is hosted by Mixpanel and authenticated via OAuth — your existing Mixpanel project permissions are automatically applied. The MCP server grants read and write access to your Mixpanel project; it can create and modify dashboards, reports, and feature flags. Treat Service Account credentials as secrets; do not commit them to repositories.✓`create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions. Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming.✓Feature flag operations include create, update (patch), and delete — changes affect live targeting rules for all users in the environment. Audit log and code reference reads are non-destructive, but flag patch and delete operations are irreversible and will affect production traffic immediately. Scope the API key to the minimum required permissions (read-only for analysis workflows, write only for flag management workflows).✓Tools can create, update, and delete feature flags, targeting rules, environments, and segments — changes affect live feature flag configuration. Use `list-staleflags` before deleting flags to identify zombie flags and avoid breaking active SDKs.
Privacy notes✓Queries and analytics results (event data, user properties, funnel metrics) are sent through Mixpanel's hosted MCP infrastructure. Session replay summaries and user segment data may surface in Claude's context — treat these as sensitive product analytics.✓Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context. Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files.✓Feature flag definitions, targeting rules, user segments, AI config prompts, environment configurations, and audit log entries from your LaunchDarkly project are surfaced in Claude's context. Your API key is passed as a CLI argument — store it in Claude Code's MCP config rather than in shell history; rotate keys from the LaunchDarkly Authorization page.✓Feature flag configurations, targeting rules, audience segments, SDK keys, and audit log entries from your ConfigCat account are surfaced in Claude's context. `CONFIGCAT_API_USER` and `CONFIGCAT_API_PASS` are Management API credentials — keep them in the MCP config env and never commit them to version control.
Prerequisites
  • A Mixpanel account — authenticate via OAuth when prompted on first tool use.
  • EU customers should use `https://mcp-eu.mixpanel.com/mcp`; India customers `https://mcp-in.mixpanel.com/mcp`.
  • Service Account credentials (Beta) are available for headless/CI use.
  • An MCP client such as Claude Code or Claude Desktop.
  • A GrowthBook account (cloud at growthbook.io or self-hosted).
  • A GrowthBook API key (from API Keys settings or a Personal Access Token with appropriate permissions).
  • Your GrowthBook account email (used when creating experiments and feature flags).
  • Node.js with `npx` available.
  • A LaunchDarkly account and an API key from the LaunchDarkly Authorization page (Settings → Authorization → API Keys).
  • Node.js (v18+) with `npx` available, and an MCP client such as Claude Code or Claude Desktop.
  • A ConfigCat account — log in at app.configcat.com.
  • Management API credentials: My Account → Public API Credentials → + Create new credentials (these are separate from SDK keys).
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add --transport http mixpanel https://mcp.mixpanel.com/mcp
claude mcp add growthbook -e GB_API_KEY=your-api-key -e GB_EMAIL=you@example.com -- npx @growthbook/growthbook-mcp
claude mcp add launchdarkly -- npx -y --package @launchdarkly/mcp-server -- mcp start --api-key YOUR_API_KEY
claude mcp add configcat -e CONFIGCAT_API_USER=<your-api-user> -e CONFIGCAT_API_PASS=<your-api-pass> -- npx -y @configcat/mcp-server
Config
{
  "mcpServers": {
    "mixpanel": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.mixpanel.com/mcp"]
    }
  }
}
{
  "mcpServers": {
    "growthbook": {
      "command": "npx",
      "args": ["@growthbook/growthbook-mcp"],
      "env": {
        "GB_API_KEY": "your-api-key",
        "GB_EMAIL": "you@example.com",
        "GB_API_URL": "https://api.growthbook.io",
        "GB_APP_ORIGIN": "https://app.growthbook.io"
      }
    }
  }
}
{
  "mcpServers": {
    "LaunchDarkly": {
      "command": "npx",
      "args": ["-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start", "--api-key", "YOUR_API_KEY"]
    }
  }
}
{
  "mcpServers": {
    "configcat": {
      "command": "npx",
      "args": ["-y", "@configcat/mcp-server"],
      "env": {
        "CONFIGCAT_API_USER": "<your-api-user>",
        "CONFIGCAT_API_PASS": "<your-api-pass>",
        "CONFIGCAT_BASE_URL": "https://api.configcat.com"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.