Skip to main content
Book a demo

Connect Mixpanel to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Mixpanel to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI 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 GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Mixpanel’s 67 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI 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 GitHub Copilot CLI

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

Tools

67 Mixpanel tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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 GitHub Copilot CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot CLI 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 GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination