Bring Ab Testing
to Cursor
Learn how to connect VWO to Cursor 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 Cursor?
Cursor's Agent mode turns VWO into an in-editor superpower. Ask Cursor to generate code using live data from VWO and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
VWO in Cursor
VWO and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect VWO to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.