4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
GrowthBook MCP Server

Bring Feature Flags
to CrewAI

Learn how to connect GrowthBook to CrewAI and start using 15 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
Create EnvironmentCreate FeatureCreate ProjectDelete EnvironmentDelete FeatureDelete ProjectGet FeatureGet ProjectList EnvironmentsList FeaturesList ProjectsToggle FeatureUpdate EnvironmentUpdate FeatureUpdate Project

Compatible with every major AI agent and IDE

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

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

  1. Subscribe to this server
  2. Enter your GrowthBook Secret Key
  3. 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 CrewAI?

When paired with CrewAI, GrowthBook becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GrowthBook tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

GrowthBook in CrewAI

AI AgentVinkius
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 CrewAI 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 GrowthBook in CrewAI

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 CrewAI 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.

GrowthBook
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 CrewAI

Every tool call from CrewAI 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

01

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.

02

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.

03

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.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →