vwo_create_ feature_ flagCreate a feature flag.
Ask which running test is closest to a winner, set up a new test with its goals, pause a campaign once you say so, or roll a feature flag out to more people, in the VWO workspace you already use.
PopMCPVWO
Every endpoint in VWO's REST API reference is a tool, from campaigns and variations to feature flags, metric reports, websites, users and attribute lists. The everyday ones load by default and the rest are one search away. Finding a test by name or status takes one call, and flat inputs and plain dates are turned into what VWO expects.
82 tools in the full catalog: 43 read and 39 write. 37 load by default, and the rest are found with tool search.
vwo_create_ feature_ flagCreate a feature flag.
vwo_create_ feature_ flag_ ruleAdd a rule to a feature flag in one environment.
vwo_get_ feature_ flagOne feature flag by id or key (featureKey).
vwo_list_ feature_ flag_ rulesA feature flag's rules in one environment: rollouts, tests and personalization.
vwo_list_ feature_ flagsList Feature Experimentation feature flags: id, featureKey, name, featureType, variables, rulesCount, variations and goals.
vwo_list_ projectsFeature Experimentation projects and their environments: ids, names and languages.
vwo_toggle_ feature_ flagTurn a feature flag on or off in one environment.
vwo_list_ widgetsList reusable custom widgets (pop-ups, banners and other HTML, JS and CSS snippets).
vwo_create_ campaignCreate a campaign.
vwo_find_ campaignsFind campaigns by part of their name, status or type.
vwo_get_ campaignOne campaign in full: status, traffic, URLs, thresholds, variations, goals and sections, and when VWO has it, results in variationGoalData (visitorCount, conversionCount, conversionRate, isWinner, isLoser per variation and goal).
vwo_get_ campaign_ share_ linkA link to the campaign's report that opens without signing in.
vwo_list_ campaignsList campaigns (A/B, multivariate, split URL, heatmap, conversion tests and more): id, name, type, status, primaryUrl, goals, variations and labels.
vwo_update_ campaignChange a campaign's settings: name, URLs, traffic percentage, thresholds.
vwo_update_ campaign_ statusStart, pause, stop, trash or restore one or more campaigns.
vwo_get_ website_ smartcodeThe SmartCode snippet to paste into one website's pages.
vwo_list_ websitesWebsites registered in the workspace: id, name, domain, platform, archived or not, and status.
vwo_create_ campaign_ goalAdd a goal to a campaign.
vwo_create_ campaign_ variationAdd a variation.
vwo_get_ campaign_ variationOne variation.
vwo_get_ workspaceThe connected workspace: id, name, created time (Unix seconds), timezone, company details and whether it is enabled.
vwo_list_ campaign_ goalsA campaign's goals: id, name, type, urls, cssSelectors and which one is primary.
vwo_list_ campaign_ variationsA campaign's variations: id, name, isControl, isDisabled, percentSplit (traffic share), the editor changes, and sectionId.
vwo_list_ usersPeople in the workspace: id, name, email, permission (Admin, Publish, Design, Browse), created time.
vwo_list_ workspace_ feedThe workspace's activity timeline, newest first: who started, paused or changed which campaign and when.
vwo_update_ campaign_ goalChange a goal.
vwo_update_ campaign_ variationChange a variation's name, percentSplit or code.
vwo_add_ campaign_ labelsPut labels on a campaign.
vwo_get_ draftOne draft in full, including its variations and segment.
vwo_get_ thresholdsWhen VWO calls a variation a winner or a loser in this workspace: winningPercent, losingPercent (percent) and the minimum visitors.
vwo_list_ draftsCampaigns still being set up: draftId, type, name, urls, who made them and which step they reached.
vwo_list_ labelsAll labels in the workspace: id and name.
vwo_get_ metric_ reportOne metric report with its numbers: visitorData holds the aggregated and per-interval totalRevenue and conversionCount, dataIntervalRange the period covered.
vwo_get_ page_ overviewHow one page behaves: experience score, friction score, session count, rage clicks and dead clicks, overall and per interval.
vwo_list_ metric_ reportsList metric reports (insights metrics): id, name, status, the date range and goals.
vwo_list_ insight_ toolsList VWO's own AI tools: daily campaign data, heatmap and recording analysis, sample size and more.
vwo_run_ insight_ toolRun one of VWO's own AI tools by name.
vwo_delete_ feature_ flagDelete a feature flag by id or key.
vwo_delete_ feature_ flag_ ruleDelete a rule of a feature flag.
vwo_get_ feature_ flag_ ruleOne rule of a feature flag, by id or key.
vwo_toggle_ feature_ flag_ ruleTurn one rule on or off.
vwo_update_ feature_ flagChange a feature flag's name, description, goals, variables or variations.
vwo_update_ feature_ flag_ ruleChange a rule's traffic or variations.
vwo_create_ widgetCreate a custom widget.
vwo_create_ widgets_ bulkCreate several custom widgets in one request.
vwo_delete_ widgetDelete a widget.
vwo_get_ widgetOne custom widget with its code.
vwo_list_ widget_ campaignsWhich campaigns use a widget.
vwo_update_ widgetReplace a widget.
vwo_update_ widgets_ bulkUpdate several global widgets in one request.
vwo_get_ websiteOne website.
vwo_get_ website_ smartcode_ settingsA website's SmartCode settings: codeType, settingsTimeout and libraryTimeout (milliseconds), useJquery, rocketLoader, hideBodyHtml.
vwo_get_ workspace_ smartcodeThe workspace's sync and async SmartCode snippets.
vwo_update_ website_ smartcode_ settingsChange a website's SmartCode settings.
vwo_create_ campaign_ sectionAdd a section to a multivariate campaign.
vwo_create_ userAdd a person to the workspace, with a password and permission level.
vwo_create_ workspaceCreate a new workspace under the main account.
vwo_delete_ campaign_ goalRemove a goal from a campaign, with its data.
vwo_delete_ campaign_ sectionDelete a section from a multivariate campaign.
vwo_delete_ campaign_ variationDelete a variation.
vwo_delete_ userRemove a person from the workspace.
vwo_get_ campaign_ goalOne goal of a campaign.
vwo_get_ campaign_ sectionOne section of a multivariate campaign.
vwo_get_ userOne person in the workspace.
vwo_list_ campaign_ sectionsA multivariate campaign's sections: id, name, cssSelector and each section's variations.
vwo_list_ workspacesThe connected workspace: id, name, created time and whether it is enabled.
vwo_update_ campaign_ sectionChange a section of a multivariate campaign.
vwo_update_ userChange a person's details or permission level (Admin, Publish, Design, Browse).
vwo_update_ workspaceChange the connected workspace: name, timezone (such as Asia/Kolkata), enabled, company name, website, size (1-200, 201-500, 501-1000, 1001-2000, 2000+) and industry type (ecommerce, saas, media, agency, travel, ngo, entertainment, banking, businessConsulting, health, education).
vwo_delete_ campaign_ labelTake a label off a campaign.
vwo_delete_ draftDelete a draft campaign.
vwo_delete_ integration_ connectionDisconnect one third-party integration from the workspace.
vwo_get_ billing_ detailsThe account's billing details: payment processor, customer name, address and payment method.
vwo_get_ invoiceOne billing cycle's invoice as a PDF, returned as base64.
vwo_get_ partner_ detailsPartner programme numbers for an account in it: users referred, sales, commission and referral code.
vwo_list_ billing_ cyclesBilling cycles: dates, visitors allowed, plan and invoice.
vwo_list_ campaign_ labelsThe labels on one campaign.
vwo_list_ integrationsThe third-party integrations set up for the workspace (Google Analytics, Tag Manager and others) and their connections.
vwo_update_ draftReplace a draft's content.
vwo_update_ thresholdsChange when VWO calls a winner or a loser for this workspace.
vwo_create_ attribute_ listCreate a list attribute for audience targeting from a list of values.
vwo_update_ attribute_ listReplace all the values of a list attribute, and optionally its name or description.
Authorize once, then an endpoint your client signs into. Nothing to deploy, and nothing to install on the VWO side.
Open VWO in PopMCP, click Connect VWO, sign in and choose a permission level on VWO's screen. If you can reach several workspaces, choose the one this connection is for. There is no developer app or callback URL to set up. VWO lists its API under the Enterprise plan. If you would rather use an API token from Developers, Tokens in VWO, it goes under More options.
your-vwo-value••••••••••••3f7aReading changes nothing. Starting or pausing a test, turning a flag on or off and editing a running campaign reach real visitors at once, so they are writes, and they wait until an owner or admin allows write actions; new connections start read-only. Each connection reaches one workspace, and a request for another is refused. SDK keys and card details are kept from the AI.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your VWO credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Which of my running tests is closest to a winner, and how is each variation doing on its main goal?
vwo_find_campaignsok
Then just ask for the work
“Which of my running tests is closest to a winner, and how is each variation doing on its main goal?”
“Set up an A/B test on our pricing page with a goal for reaching checkout, and leave it unstarted so I can review it”
“Pause the homepage headline test and tell me who last changed it”
“Which feature flags are on in production, and what rules do they have?”
“How is our checkout page doing on rage clicks and friction this month?”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting VWO behind an AI client.
Yes. VWO merged with AB Tasty and now goes by Wingify, and vwo.com leads to wingify.com. It is the same product and the same login, so sign in with the account you already have.
No. Click Connect VWO, sign in and approve. PopMCP is already registered with VWO, so there is no developer app, secret or callback URL. If you prefer a token, make one under Developers, Tokens in VWO and use More options on the connect form.
VWO's help centre says its API is only available on the Enterprise plan. If VWO refuses access when you connect, check your workspace's plan with your VWO contact.
Only if you allow write actions and ask for it. New connections start read-only. With writes on, the AI is told to name the test and the change and ask you first, because a status change or an edit to a running test reaches real visitors at once. Choosing Browse on VWO's screen blocks changes on VWO's side too.
You choose one when you connect, and that connection only reaches that workspace. A request for another is refused. To work with a second workspace, connect it as a second connection.
VWO allows one request per second for each token and asks for a minute's wait after going over. PopMCP makes requests take turns, so an AI calling several tools at once stays inside the limit.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect VWO in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking VWO on the consent screen. The VWO tools are then available in that session, and no VWO credential is stored on your machine.
Loading 82 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 37-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 82 here. A trigger is something PopMCP watches for you: 8 VWO events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into VWO.
Launch a hosted MCP endpoint for VWO, keep tool access under control, and start testing real workflow prompts right away.