Bring Ab Testing
to VS Code Copilot
Learn how to connect VWO to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings VWO data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
VWO in VS Code Copilot
VWO and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect VWO 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.
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 VS Code Copilot
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 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.
* 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.