An astronaut overseeing a futuristic data hub

Connect Statsig to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage feature rollouts and configs through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 12 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 12 available through Statsig.

  1. 01

    Get config

    This capability pulls configuration values for a specific dynamic config or experiment. It uses your Statsig Server Secret Key to fetch the data.

  2. 02

    Get gate

    This capability reads a specific feature gate. It requires your Statsig Console API Key.

  3. 03

    Get layer

    This capability retrieves parameter values from a specific layer. It uses your Statsig Server Secret Key.

  4. 04

    Create dynamic config

    This capability creates a new dynamic config in your project using the Statsig Console API Key.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through Statsig.

  1. 05

    Delete gate

    This capability removes a feature gate from your project via the Console API.

  2. 06

    Update gate

    This capability modifies an existing feature gate using your Statsig Console API Key.

  3. 07

    Check gate

    This capability evaluates one or more feature gates for a specific user. It uses your Statsig Server Secret Key.

  4. 08

    Create gate

    This capability sets up a new feature gate in your Statsig project.

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through Statsig.

  1. 09

    Get dynamic config

    This capability reads the details of a specific dynamic config using the Console API.

  2. 10

    List dynamic configs

    This capability returns a list of all dynamic configs within your project.

  3. 11

    List gates

    This capability retrieves a list of all feature gates in your Statsig project.

  4. 12

    Log event

    This capability sends custom events to Statsig for real-time analytics. It uses your Statsig Server Secret Key.

Real work

What teams actually run

01

Rapid Feature Rollouts

Toggle a feature for a specific user segment using a single chat command.

02

Experiment Debugging

Verify why a user is seeing a specific version of a feature by checking gate evaluations.

03

Config Management

Update JSON configurations for dynamic features without a new code push.

04

Analytics Verification

Log test events to ensure your custom metrics are firing as expected during a test run.

Automate a task

Put Statsig to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Statsig works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Statsig to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1032ms average. Fast in production.

Statsig is checked daily against the live service.

Daily averagePeak 1275ms
Oct 3Today
Fastest day
780ms
Slowest day
1275ms
14-day trend
Improving-22%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 12 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Statsig, so you can see the experience inside your AI.

It does not authenticate your account with Statsig. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Statsig Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_ZEX4bsyQXMNxXPnw9oDygkK22SmvaLyaVC4MgykQ/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Statsig capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "statsig-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ZEX4bsyQXMNxXPnw9oDygkK22SmvaLyaVC4MgykQ/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Statsig in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Statsig owners hand off.

This MCP is built for teams running continuous experimentation and feature rollouts.

  • 01

    Product Managers

    They use the agent to check gate statuses and create new flags without opening the Statsig console.

  • 02

    Developers

    They use the agent to verify evaluation logic and log test events directly from their IDE.

  • 03

    Data Scientists

    They use the agent to inspect experiment configurations and confirm metric logging.

FAQ

Questions Statsig owners ask.

  • 01

    What keys do I need for this MCP?

    You will need your Statsig Server Secret Key for evaluating gates and your Console API Key for managing gates and configs.

  • 02

    Can I use this with Cursor or VS Code?

    Yes, this MCP works with any MCP-compatible client, including Cursor, Windsurf, and VS Code.

  • 03

    Does this allow me to change feature flags?

    Yes, you can create, update, and delete feature gates and dynamic configs through your agent.

  • 04

    How do I log events to Statsig?

    You can use the log_event capability to send custom events for real-time analytics directly from your chat interface.

  • 05

    Is my data hosted by Vinkius?

    Vinkius hosts the MCP and manages the connection and credentials so it is ready to use immediately.

  • 06

    What is the difference between the Server Secret Key and the Console API Key?

    The Server Secret Key is used for evaluation capabilities like check_gate and get_config. The Console API Key is required for management actions like list_gates or create_gate.

  • 07

    How do I evaluate a gate for a specific user?

    Use the check_gate capability. You must provide the gateName and a user JSON object containing at least a userID (e.g., {"userID": "123"}).

  • 08

    Can I log custom events for analytics?

    Yes, use the log_event capability to send an array of event objects including name, value, and user metadata to Statsig for real-time metric calculation.

Connect Statsig to Claude, Cursor, ChatGPT & more