Bring Ab Testing
to CrewAI
Learn how to connect VWO to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the VWO MCP Server?
Connect your VWO (Visual Website Optimizer) account to any AI agent and take control of your experimentation and feature rollout workflows through natural conversation.
What you can do
- Optimization Campaigns — List and monitor active A/B tests and personalization campaigns directly from your agent
- Feature Management — List all feature flags and toggle their status across different environments for instant rollouts
- Experiment Results — Retrieve statistical results for any campaign, including performance metrics and significance levels
- Conversion Tracking — Browse conversion goals and KPIs being tracked to understand your optimization impact
- Audience Segmentation — List pre-defined segments to see how you are targeting different user groups
- Environment Control — Manage features across staging, production, and other configured VWO environments
How it works
1. Subscribe to this server
2. Enter your VWO API Token and Account ID
3. Start managing your experiments and feature flags through Claude, Cursor, or any MCP-compatible client
No more jumping between experiment dashboards to check test results. Your AI agent becomes your optimization engine.
Who is this for?
- Growth Managers — monitor experiment results and statistical significance without manual data exports
- Product Managers — manage feature rollouts and toggle flags across environments during launches
- Data Analysts — quickly surface conversion goal metrics and audience segment performance
- CRO Specialists — audit active campaigns and identify optimization opportunities through simple chat commands
Built-in capabilities (10)
Retrieves details for a specific VWO campaign
Retrieves statistical results for a VWO campaign
Retrieves configuration for a specific VWO feature flag
Retrieves details about the authenticated VWO account
Lists all audience segments
g. clicks, revenue) are being tracked. Lists all conversion goals and metrics
Lists all VWO feature flags
Lists all VWO A/B test and personalization campaigns
g. Production, Staging) for feature flag management. Lists all configured VWO environments
Provide the feature ID and the desired enabled status (true/false). Enables or disables a VWO feature flag
Why CrewAI?
When paired with CrewAI, VWO becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call VWO 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
VWO in CrewAI
VWO and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect VWO 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 | 3,400+ 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 VWO in CrewAI
The VWO 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 10 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
VWO for CrewAI
Every tool call from CrewAI to the VWO MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the winning variation of an A/B test through the agent?
Yes. The get_campaign_results tool allows your AI agent to pull detailed performance metrics for any experiment, showing improvement percentages and statistical significance for each variation compared to the control.
Is it possible to enable or disable feature flags via chat?
Absolutely. Using the toggle_feature_flag tool, you can instruct your agent to enable or disable any feature flag for a specific rollout or emergency kill-switch scenario, ensuring fast control without opening the VWO dashboard.
How can I see what conversion goals are being tracked for my campaigns?
You can use the list_conversion_goals tool to retrieve all metrics and KPIs (like clicks, form submissions, or revenue) currently being monitored in your VWO account.
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.