4,000+ servers built on vurb.ts
Vinkius
AutoGenFramework
AutoGen
Statsig MCP Server

Bring Feature Flags
to AutoGen

Learn how to connect Statsig to AutoGen and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Check GateCreate Dynamic ConfigCreate GateDelete GateGet ConfigGet Dynamic ConfigGet GateGet LayerList Dynamic ConfigsList GatesLog EventUpdate Gate

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Statsig

What is the Statsig MCP Server?

Connect your Statsig project to any AI agent to manage feature rollouts and product experiments through natural conversation.

What you can do

  • Feature Gates — Evaluate if a feature is enabled for a specific user or list all project gates
  • Dynamic Configs — Fetch JSON configurations and experiments to control app behavior without code changes
  • Event Logging — Log custom events for real-time analytics and metric calculation
  • Gate Management — Create, update, or delete feature gates directly via the Console API
  • Layer Inspection — Evaluate layers and retrieve parameter values for specific users

How it works

  1. Subscribe to this server
  2. Enter your Statsig Server Secret Key (for evaluation) and Console API Key (for management)
  3. Start managing your product experiments from Claude, Cursor, or any MCP client

Who is this for?

  • Product Managers — check gate statuses and create new feature flags without leaving the chat
  • Developers — verify evaluation logic and log test events directly from the IDE
  • Data Scientists — inspect experiment configurations and verify metric logging

Built-in capabilities (12)

check_gate

Requires STATSIG_SERVER_SECRET_KEY. Evaluates one or more feature gates for a user

create_dynamic_config

Requires STATSIG_CONSOLE_API_KEY. Create a new dynamic config

create_gate

Requires STATSIG_CONSOLE_API_KEY. Create a new feature gate

delete_gate

Requires STATSIG_CONSOLE_API_KEY. Delete a feature gate

get_config

Requires STATSIG_SERVER_SECRET_KEY. Fetches configuration values for a dynamic config or experiment

get_dynamic_config

Requires STATSIG_CONSOLE_API_KEY. Read a specific dynamic config

get_gate

Requires STATSIG_CONSOLE_API_KEY. Read a specific feature gate

get_layer

Requires STATSIG_SERVER_SECRET_KEY. Fetches parameter values from a layer

list_dynamic_configs

Requires STATSIG_CONSOLE_API_KEY. List all dynamic configs in the project

list_gates

Requires STATSIG_CONSOLE_API_KEY. List all feature gates in the project

log_event

Requires STATSIG_SERVER_SECRET_KEY. Logs custom events for analytics and metric calculation

update_gate

Requires STATSIG_CONSOLE_API_KEY. Update an existing feature gate

Why AutoGen?

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Statsig tools. Connect 12 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

  • Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Statsig tools to solve complex tasks

  • Role-based architecture lets you assign Statsig tool access to specific agents. a data analyst queries while a reviewer validates

  • Human-in-the-loop support: agents can pause for human approval before executing sensitive Statsig tool calls

  • Code execution sandbox: AutoGen agents can write and run code that processes Statsig tool responses in an isolated environment

A
See it in action

Statsig in AutoGen

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Statsig and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Statsig to AutoGen through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Statsig in AutoGen

The Statsig MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in AutoGen only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Statsig
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Statsig for AutoGen

Every tool call from AutoGen to the Statsig MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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

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

02

How do I evaluate a gate for a specific user?

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

03

Can I log custom events for analytics?

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

04

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Statsig tools during their conversation turns.

05

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.

06

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

07

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Explore More MCP Servers

View all →