Skip to main content
Book a demo

Connect Mixpanel to VS Code

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

Book a demo VS Code setup guide

Set up

Add Mixpanel to VS Code in four steps

Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Mixpanel’s 67 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code 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 VS Code

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

Tools

67 Mixpanel tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 before VS Code runs it.

  • Block output after it runs (available)

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

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination