VS Code CopilotIDE

GrowthBook MCP Server

Bring Feature Flags
to VS Code Copilot

Name: GrowthBook MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect GrowthBook to VS Code Copilot and start using 15 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Create EnvironmentCreate FeatureCreate ProjectDelete EnvironmentDelete FeatureDelete ProjectGet FeatureGet ProjectList EnvironmentsList FeaturesList ProjectsToggle FeatureUpdate EnvironmentUpdate FeatureUpdate Project

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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_environment

Create a new GrowthBook environment

create_feature

Create a new GrowthBook feature flag (v2)

create_project

Create a new GrowthBook project

delete_environment

Delete a GrowthBook environment

delete_feature

Delete a GrowthBook feature flag (v2)

delete_project

Delete a GrowthBook project

get_feature

Get a single GrowthBook feature flag (v2)

get_project

Get a single GrowthBook project by ID

list_environments

g., production, staging) used for per-environment feature flag control. List all GrowthBook environments

list_features

List all GrowthBook feature flags (v2)

list_projects

List all GrowthBook projects

toggle_feature

Toggle a GrowthBook feature flag on or off

update_environment

Update an existing GrowthBook environment

update_feature

Partially update a GrowthBook feature flag (v2)

update_project

Edit an existing GrowthBook project

Why VS Code Copilot?

GitHub Copilot Agent mode brings GrowthBook data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 15 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

GrowthBook in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

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

Teams that connect GrowthBook to VS Code Copilot 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 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

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for GrowthBook in VS Code Copilot

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 VS Code Copilot 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.

Unlock for AI Agents View full GrowthBook details →

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
GrowthBook for VS Code Copilot

Every tool call from VS Code Copilot to the GrowthBook 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

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.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.