Bring Feature Flags
to CrewAI
Learn how to connect Statsig to CrewAI 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 CrewAI?
When paired with CrewAI, Statsig becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Statsig 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
mcpsparameter 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
Statsig in CrewAI
Statsig and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Statsig 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.
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 CrewAI
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 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.
* 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 CrewAI
Every tool call from CrewAI 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 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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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 →
Time MS Converter
1 toolsStop AI math hallucinations. Convert human-readable time (e.g., '2 days', '1.5h') into exact milliseconds for DevOps scheduling.
Captain Data
11 toolsAutomate web data extraction via Captain Data — find and enrich people and company profiles directly from any AI agent.
DocSumo
10 toolsEquip your AI agent to automate document data extraction, manage IDP workflows, and audit processed files via the DocSumo API.
Mixmax
10 toolsAccelerate your sales cycle with Mixmax — sequences, scheduling, and email tracking.