Beta. MCP Connections are currently available to a limited set of customers during Beta. If you’d like to participate, reach out to your Mixpanel account team.
Overview
MCP Connections let Mixpanel Agent read context from the tools your team already uses. Each connection links your own account on an external Model Context Protocol (MCP) server to Mixpanel, so the Agent can pull in issues, pull requests, docs, and tickets alongside your Mixpanel data. MCP Connections are the reverse of the Mixpanel MCP Server: the MCP Server lets outside AI tools read Mixpanel, while MCP Connections let Mixpanel Agent read outside tools. Key properties:- Read-only. Mixpanel Agent can only use read tools on connected servers. It cannot create, edit, or delete anything in them.
- Private to you. Connections belong to your user in a single organization. Teammates cannot see or use your connections, and the Agent sees only what your account on that tool can see.
- Removed when you leave. If you are removed from the organization, your connections and their credentials are deleted.
Supported Tools
Each tool can be connected once per user.
Enable MCP Connections for Your Organization
MCP Connections are off by default. An organization admin or owner must turn them on before anyone can connect a tool.- Go to Settings → Org → AI Settings.
- Make sure Enable Mixpanel AI is on. MCP Connections require Mixpanel AI.
- Turn on Connect Your Tools via MCP.
Add a Connection
- Go to Settings → Personal Settings → MCP Connections. You can also add a connection from the MCP Connections menu in the Mixpanel Agent chat box.
- Click Add Connection and choose a tool.
- Mixpanel checks how the server handles authentication, then asks you to sign in in one of two ways:
- OAuth: Servers that support OAuth open a popup to their own sign-in page. Sign in, approve access, and the popup confirms “Successfully connected”. Notion, Linear, and Jira work this way.
- Token: Servers that don’t support OAuth sign-in with Mixpanel ask you to paste a token in the Authentication Token field. Mixpanel checks the token before saving it. GitHub works this way.
Use Connections in Mixpanel Agent
Your connections are available in every Mixpanel Agent conversation. To choose which ones the Agent can use in a conversation, open the MCP Connections menu in the chat box and check or uncheck each connection. Example prompts:- Signups dropped on Tuesday. Were any pull requests merged to the signup service that day?
- Summarize the open Jira tickets about the checkout flow and show me the checkout funnel for the same period.
- Find the Notion spec for the new onboarding flow and check whether we track every step it describes.
Manage Connections
The Connection Status column on the MCP Connections page checks each connection when you open the page:- Connected: The connection is working.
- Disconnected: The credentials are no longer valid, for example because a token expired or was revoked, or you revoked access in the tool.
- Unavailable: An admin has turned off Connect Your Tools via MCP for your organization.