How can I integrate mixpanel MCP in a kubernetes server, how auth will work
How can I integrate mixpanel MCP in a kubernetes server, how auth will work
How can I integrate mixpanel MCP in a kubernetes server, how auth will work
Integrating Mixpanel MCP in a Kubernetes Server
The knowledge sources do not explicitly cover Kubernetes-specific deployment of the Mixpanel MCP server. However, based on the available documentation, here's what applies to your use case:
MCP Server Connection (Kubernetes Context)
Since Kubernetes workloads typically use JSON-configured or CLI-based clients, the most relevant integration approach would be using the Streamable HTTP method. You would configure your client/agent to point to the MCP server URL:
US: https://mcp.mixpanel.com/mcp
EU: https://eu.mixpanel.com/mcp
IN: https://in.mixpanel.com/mcp
For any JSON-configured client running in your cluster, you can use a config like:
{
"mcpServers": {
"mixpanel": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.mixpanel.com/mcp"]
}
}
}Authentication
Authentication uses OAuth 2.0 with Authorization Code + PKCE (S256). Key details:
Authorization endpoint: https://{mixpanel_domain}/oauth/authorize
Token endpoint: https://{mixpanel_domain}/oauth/token/
Grant types: authorization_code, refresh_token
Code challenge method: S256
For building a custom integration (which is likely what you'd need in a Kubernetes environment), you can use dynamic client registration:
Region | Registration Endpoint |
US | https://mixpanel.com/oauth/mcp/register/ |
EU | https://eu.mixpanel.com/oauth/mcp/register/ |
IN | https://in.mixpanel.com/oauth/mcp/register/ |
You can also discover OAuth endpoints via well-known URLs:
https://mcp.mixpanel.com/.well-known/oauth-protected-resource/mcp
https://mcp.mixpanel.com/.well-known/oauth-authorization-server/mcpPermissions & Prerequisites
An organization admin must enable MCP in Settings → Org → Overview before any connection works (changes take up to 15 minutes). [Permissions & Access]
Users authenticate with their own Mixpanel credentials, so existing project permissions and roles are respected.
The MCP server inherits all existing Mixpanel governance settings (Data Views, classified properties, project access scoping). [Permissions Q&A]
Important Caveat
The knowledge sources do not provide specific guidance on Kubernetes deployment patterns (e.g., running mcp-remote as a sidecar, managing OAuth tokens as Kubernetes secrets, or handling token refresh in a pod). For those specifics, you would need to consult Kubernetes documentation alongside the OAuth flow details above.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.