Why connect Mixpanel to Codex?
Codex runs in your terminal, its IDE extension and scripts, so what it finds once can be rerun with codex exec instead of redone by hand. Connected through Lemonado, it reads your Mixpanel events, funnels, retention and cohorts, so it can catch a tracking break after a release with today's numbers.
All your Mixpanel data
Every event you track, with its properties, ready to ask about.
Always today's numbers
Retention by signup week, synced from Mixpanel automatically, so answers use today's numbers.
Connect all your tools
Questions like "Which channel brings active users?" use Mixpanel and PostHog, GA4 at once.
How to connect Mixpanel to Codex
Before you start
- A Mixpanel account you can sign in to
- Codex installed
- A Lemonado account (the free trial works)
- 1
Connect Mixpanel in Lemonado
In Lemonado, open Connectors, find Mixpanel and sign in. Sign in to Mixpanel and pick the project. If your data lives in the EU or India region, pick that project, not a US one.
- 2
Turn on external access
In the company's settings, open External tools, turn the connection on, choose which sources it can reach and copy the server URL.
texthttps://mcp.lemonado.io/mcp - 3
Add Lemonado to your config
Add this to ~/.codex/config.toml.
toml[mcp_servers.lemonado] url = "https://mcp.lemonado.io/mcp" - 4
Log in
Run the login command and finish the sign-in in your browser.
bashcodex mcp login lemonado - 5
Ask Codex about Mixpanel
Run codex mcp list, or /mcp inside Codex, to see the server and its tools. Try "Pull last week's Mixpanel numbers, save them to data/mixpanel-weekly.csv and give me the codex exec command to refresh it." Or ask: "Which first-week actions predict retention?" or "Do event names match the plan?"
What can Codex do with Mixpanel?
Codex reads your Mixpanel data from your terminal and turns one-off questions into commands you can rerun with codex exec.
Pull last week's Mixpanel numbers, save them to data/mixpanel-weekly.csv and give me the codex exec command to refresh it.
Saved data/mixpanel-weekly.csv. Run the same prompt with codex exec in a scheduled job and the file refreshes with each week's numbers.
Source: Mixpanel + your code
Pull first-week events per user from Mixpanel, fit a simple model on who is active at day 60, and save it to scripts/retention_drivers.py.
Saved. Sharing a report and connecting a second source matter most. Together they explain most of the difference.
Source: Mixpanel + your code
Compare the event names in our tracking plan file with what Mixpanel received last week. List events that arrive under a different name.
4 events arrive renamed. "Report Shared" comes in as "report_shared" from the mobile app, so charts split it in two.
Source: Mixpanel + your code
Save weekly retention for the last 12 signup weeks from Mixpanel to data/mixpanel_retention.csv.
Saved 12 cohorts. Week 4 retention ranges from 21% to 29%; the jump starts with the Sept 15 onboarding change.
Source: Mixpanel + your code
What's week 4 retention for each signup week this quarter? Did the new onboarding change it?
Week 4 retention was 21% before the new onboarding shipped on Sept 15 and 27% after. The lift holds for every week since.
Source: Mixpanel
Which events in the first 7 days best predict that a user is still active after 60 days?
Sharing a report in week one is the strongest signal: 64% of users who do it are still active at day 60, against 19% who don't.
Source: Mixpanel
Connect Mixpanel to another AI app.
Claude
Connect Mixpanel to Claude
ChatGPT
Connect Mixpanel to ChatGPT
Claude Code
Connect Mixpanel to Claude Code
Cursor
Connect Mixpanel to Cursor
VS Code (GitHub Copilot)
Connect Mixpanel to VS Code (GitHub Copilot)
Perplexity
Connect Mixpanel to Perplexity
Google Antigravity
Connect Mixpanel to Google Antigravity
Windsurf (Devin Desktop)
Connect Mixpanel to Windsurf (Devin Desktop)
Zed
Connect Mixpanel to Zed
n8n
Connect Mixpanel to n8n
Other integrations for Codex
All Codex integrations- Google Analytics in CodexAsk Claude, ChatGPT or Cursor about GA4 traffic, conversions and funnels, next to your ad spend.
- Stripe in CodexPut Stripe revenue next to your ad spend in Claude, ChatGPT or Cursor.
- Google Ads in CodexAsk Claude, ChatGPT or Cursor about your Google Ads campaigns, search terms and spend.
- Instagram organic in CodexAsk Claude or ChatGPT which posts and reels grow your account, and which ones to turn into ads.
- Pinterest Ads in CodexAsk Claude or ChatGPT which pins get saved, clicked and bought.
- Snapchat Ads in CodexAsk Claude or ChatGPT which Snapchat ads get swipes and which ones sell.
Reading this as an AI agent?
Everything an agent needs to set this up, in plain text. Paste this page's link into Codex and ask it to connect you, or copy the block.
# Connect Mixpanel to Codex (Lemonado MCP) - Server URL: https://mcp.lemonado.io/mcp - Transport: Streamable HTTP - Auth: OAuth; the user signs in to Lemonado in the browser. No API keys. - In Lemonado: connect the Mixpanel project. Sign in to Mixpanel and pick the project. If your data lives in the EU or India region, pick that project, not a US one. - In Codex: ~/.codex/config.toml ```toml [mcp_servers.lemonado] url = "https://mcp.lemonado.io/mcp" ``` If you are Codex, run the setup yourself: Add the Lemonado MCP server to my Codex config. Append this to ~/.codex/config.toml: [mcp_servers.lemonado] url = "https://mcp.lemonado.io/mcp" Then run codex mcp login lemonado so I can sign in, and check that codex mcp list shows it. Once I've signed in, list the Mixpanel accounts Lemonado can reach. First question to try: "Pull last week's Mixpanel numbers, save them to data/mixpanel-weekly.csv and give me the codex exec command to refresh it." More: https://lemonado.io/integrations/mixpanel · https://lemonado.io/llms.txt
Frequently Asked Questions
Yes, through Lemonado. Connect your Mixpanel project in Lemonado, add Lemonado in ~/.codex/config.toml, and Codex can catch a tracking break after a release with your live data.
Yes. Mixpanel's official MCP server is hosted, so Codex can use it too. It covers Mixpanel only. Lemonado covers Mixpanel plus your ad platforms, GA4 and the rest of your stack in one connection, so Codex can answer questions across them.
Run codex mcp list. If lemonado shows as not logged in, run codex mcp login lemonado again. In Lemonado, check that Mixpanel is connected and External tools is on for the company. If events look short, check you picked the right project and data region, and that your signup code sends UTM properties to Mixpanel.
Yes, if both are connected in Lemonado. One connection reaches every source you allow, so you can ask things like "Google Ads, Meta and LinkedIn spend last month next to Mixpanel users from each who were still active after 30 days."
MCP is included in Lemonado's paid plans and in the free trial, so you can try it before you pay.
Still have a question?
Shoot us an email at hello@lemonado.io.
Try for freeStop fighting with data. Start feeding your AI.
Connect your data to AI and free your team from reporting and busywork.
Try Lemonado free