Compatible with every major AI agent and IDE
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
- Subscribe to this server
- Enter your Statsig Server Secret Key (for evaluation) and Console API Key (for management)
- 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)
Requires STATSIG_SERVER_SECRET_KEY. Evaluates one or more feature gates for a user
Requires STATSIG_CONSOLE_API_KEY. Create a new dynamic config
Requires STATSIG_CONSOLE_API_KEY. Create a new feature gate
Requires STATSIG_CONSOLE_API_KEY. Delete a feature gate
Requires STATSIG_SERVER_SECRET_KEY. Fetches configuration values for a dynamic config or experiment
Requires STATSIG_CONSOLE_API_KEY. Read a specific dynamic config
Requires STATSIG_CONSOLE_API_KEY. Read a specific feature gate
Requires STATSIG_SERVER_SECRET_KEY. Fetches parameter values from a layer
Requires STATSIG_CONSOLE_API_KEY. List all dynamic configs in the project
Requires STATSIG_CONSOLE_API_KEY. List all feature gates in the project
Requires STATSIG_SERVER_SECRET_KEY. Logs custom events for analytics and metric calculation
Requires STATSIG_CONSOLE_API_KEY. Update an existing feature gate
Why Windsurf?
Windsurf's Cascade agent chains multiple Statsig tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 12 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 12 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
Statsig in Windsurf
Statsig and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Statsig to Windsurf 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Statsig in Windsurf
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 Windsurf 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.

* 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
How Vinkius secures
Statsig for Windsurf
Every tool call from Windsurf to the Statsig MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
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"}).
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.
How does Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.
Explore More MCP Servers
View all →
Fireflies.ai
12 toolsRecord, transcribe, and search across all your meetings with AI that captures every conversation and makes it instantly findable.

Fleetio
12 toolsManage vehicles, track maintenance, and monitor fuel entries via AI agents with Fleetio.

Feedly
12 toolsManage your news aggregation via Feedly — list collections, read streams, and search for feeds directly through your AI agent.

Rancher
10 toolsEquip your AI to manage Kubernetes environments directly through Rancher, overseeing clusters, namespaces, and active pods.
