Terminal
Terminal/Skill
Connects Mixpanel to a project through the MCP server or the headless Python SDK, so other Mixpanel skills have an engine to use.
By Mixpanel
Works with
npx skills add mixpanel/ai-plugins --skill installNo engine required — this skill is what sets engines up.
Set up how this project talks to Mixpanel. Engines can coexist — a project may have more than one; this skill adds one and can record which to prefer. How the other skills resolve an engine (the precedence ladder, preference locations) lives in ../../ENGINE.md — read it before starting.
This skill is interactive: it asks the user to choose. If the session can't ask questions (non-interactive/CI run), stop and tell the user to run /mixpanel:install in an interactive session instead.
The bundled references defer to the live Mixpanel docs they cite — on any conflict, trust the live page.
mp --version (one command). Success → the headless SDK is installed: ask "MCP is not available — how should we proceed?" with two options: (a) install MCP, (b) use headless. Installing MCP → Step 2a. Using headless → verify auth (Step 2b's verify) and jump to Step 3, including the preference note.Ask with the client's multiple-choice question UI (one question, three options):
mixpanel-headless Python package; the full Mixpanel platform as a Python object; best for scripted, CI, or coding-agent workflows.references/mcp-setup.md). If the user is unsure, their Mixpanel URL tells them (eu.mixpanel.com → EU, in.mixpanel.com → India; otherwise US).references/mcp-setup.md — the standard recipe per client, plus the fallback transport. No further questions; just run the standard installation.references/headless-setup.md; install the SDK if it's missing.mp login yourself — it picks the right flow from the environment (opens the user's browser for OAuth, or uses service-account / bearer-token env vars when set). Don't ask the user to run it; just tell them to complete the login in the browser. Credentials never go in tracked files.mp account test. On failure, surface the exact error and fix auth before wrapping up.Nothing to install and nothing to interrogate — assume the user provides the context needed to act (in the conversation, or in the project's agent instructions like CLAUDE.md). Acknowledge, skip Step 3's verification, but do offer Step 3's preference note so future sessions pick the integration up.
Always complete all three points — even when this skill was triggered mid-task by another skill, finish them before resuming the original request.
.mcp.json or the Python environment) plus any engine the project already had.For Mixpanel, use the headless SDK.) to the matching file per ../../ENGINE.md: project → the project's CLAUDE.md (or AGENTS.md in Cursor); user → ~/.claude/CLAUDE.md (in Cursor, point them to Settings → Rules). Never write without asking. A note is only needed to prefer something other than MCP.analyze-report, deep-research, or tracking-implementation. If the headless engine was installed, also mention the SDK's companion plugin (see references/headless-setup.md).