Compatible with every major AI agent and IDE
What is the GrowthBook MCP Server?
Connect your GrowthBook account to any AI agent to streamline your experimentation and feature management workflows through natural language.
What you can do
- Feature Management — List, create, and toggle feature flags across production and staging environments to control rollouts.
- Project Control — Organize your experimentation roadmap by managing projects, their descriptions, and specific settings.
- Environment Visibility — Audit and list all configured environments to ensure flags are deployed correctly across your stack.
- Full Lifecycle — Create, update, or delete projects and environments as your infrastructure and team needs evolve.
- Deep Inspection — Retrieve detailed metadata for specific features and projects to understand their current configuration and state.
How it works
- Subscribe to this server
- Enter your GrowthBook Secret Key
- Start managing flags and experiments from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Product Managers — quickly toggle features for beta testers or check the status of an experiment without opening the dashboard
- Engineering Teams — manage flags and environments directly from the code editor to maintain development flow
- DevOps Engineers — audit environment configurations and project structures via simple natural language queries
Built-in capabilities (15)
Create a new GrowthBook environment
Create a new GrowthBook feature flag (v2)
Create a new GrowthBook project
Delete a GrowthBook environment
Delete a GrowthBook feature flag (v2)
Delete a GrowthBook project
Get a single GrowthBook feature flag (v2)
Get a single GrowthBook project by ID
g., production, staging) used for per-environment feature flag control. List all GrowthBook environments
List all GrowthBook feature flags (v2)
List all GrowthBook projects
Toggle a GrowthBook feature flag on or off
Update an existing GrowthBook environment
Partially update a GrowthBook feature flag (v2)
Edit an existing GrowthBook project
Why Cursor?
Cursor's Agent mode turns GrowthBook into an in-editor superpower. Ask Cursor to generate code using live data from GrowthBook and it fetches, processes, and writes. all in a single agentic loop. 15 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
GrowthBook in Cursor
GrowthBook and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect GrowthBook 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 GrowthBook in Cursor
The GrowthBook 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 15 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
GrowthBook for Cursor
Every tool call from Cursor to the GrowthBook MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I enable or disable a feature flag using the AI?
Yes! You can use the toggle_feature tool to change the state of any flag. Simply specify the feature ID and the target environment.
How do I see which environments are available for my flags?
You can use the list_environments tool. It will retrieve all configured environments like production, staging, or development used in your GrowthBook account.
Is it possible to create a new project to group my experiments?
Absolutely. Use the create_project tool by providing a name and optional description. This helps keep your feature flags and experiments organized by team or application.
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 →
Serviceform
7 toolsConvert website visitors with chatbots, forms, and booking widgets that generate leads and collect data without friction.

Prismic
10 toolsQuery and manage your Prismic headless CMS content — search documents, list custom types, and retrieve specific content directly from any AI agent.

GAN.ai
12 toolsGenerate personalized videos at scale, track generation status, and oversee campaigns via AI agents with GAN.ai.

Howuku
10 toolsAnalyze user behavior via Howuku — track projects, recordings, and heatmaps.
