Skip to main content
Book a demo

Connect Mixpanel to Codex

Give Codex governed access to Mixpanel’s 67 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Mixpanel to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Add Mixpanel to Runlayer

    Mixpanel isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Mixpanel’s 67 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Mixpanel

    Sign in the way Mixpanel requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Mixpanel from Codex

    Mixpanel’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

67 Mixpanel tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Bulk edit events

    Uniform fields (applied to ALL events): hidden, verified, dropped,

  • Bulk edit properties

    Uniform fields (applied to ALL properties): hidden, dropped, sensitive, tags.

  • Create cohort

    Create a new Mixpanel cohort.

  • Create custom property

    Create a formula-based custom property (a computed event or user property) in a project.

  • Create dashboard

    Create a Mixpanel dashboard that combines multiple reports and text into a single view.

  • Create experiment

    Create an experiment (in DRAFT status) in the current project.

  • Create feature flag

    Create a feature flag in the current project.

  • Create lookup table

    Create a lookup table from rows.

See all 67 Mixpanel tools

Control

What Runlayer can see and stop in Codex

Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.

  • Gateway policy (available)

    Every Mixpanel call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination