Bring Feature Flags
to Cursor
Learn how to connect Statsig to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns Statsig into an in-editor superpower. Ask Cursor to generate code using live data from Statsig and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Statsig in Cursor
Statsig and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Statsig to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Splitwise
10 toolsConnect your Splitwise account to AI agents to track expenses, check balances, and manage shared groups.
Shippo
12 toolsGet the best shipping rates from top carriers, print labels, and track deliveries with an API that simplifies e-commerce shipping.
Pixso
10 toolsCollaborative design platform and UI/UX tool — manage design files, nodes, and teams via AI.
Product Hunt Alternative
4 toolsAccess Product Hunt data directly — browse daily posts, execute custom GraphQL queries, and manage your viewer profile via AI.