Is this an official VWO MCP server?

No. It is Memtro's MCP server with Memtro's VWO connector behind it: the connector reads VWO through its API with the credentials you connect on Dashboard → Connections, and VWO publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in VWO?

Only when you ask, and only what it has been granted: create a campaign (created as not started); rename a campaign; add a variation to a campaign; create a feature flag; update a feature flag's name or description; delete a feature flag; turn a feature flag on or off in an environment. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Analytics

VWO MCP server

VWO in any MCP client, through Memtro: VWO does not publish this server. Memtro's VWO connector reads VWO through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

VWO (Wingify) experimentation: workspaces, A/B and other campaigns with their status, URLs, goals and variations, websites, feature flags with their projects and environments, the workspace timeline of who started, paused or changed what, and metric reports with aggregated conversions and revenue; when you ask, can create a campaign (not started), rename a campaign, add a variation, create, update or delete a feature flag, and turn a flag on or off in an environment.

Reads

vwo_list_workspacesThe VWO workspaces this token can see, with id, name, created date and whether enabled, including the main one.
vwo_list_campaignsCampaigns in a VWO workspace: id, name, type (ab, split, multivariate, heatmap, survey...), platform, status (NOT_STARTED, RUNNING, PAUSED...)…
vwo_get_campaignOne VWO campaign in full: status, traffic percentage, URLs and exclusions, device, variations with their traffic split, and…
vwo_list_websitesWebsites registered in a VWO workspace: id, name, domain, platform, whether archived, created and last updated dates, and tracking status…
vwo_list_feature_flagsFeature flags in a VWO workspace (Feature Experimentation), and with include_environments the flag projects and their environments…
vwo_workspace_timelineThe VWO workspace's timeline, most recent first: what happened (campaign started, paused, created with N variations, settings changed), when…
vwo_metric_reportsVWO metric reports (Insights metrics): with report_id, one report with its goals and aggregated numbers (conversions…

Acts, when you ask

These change something in VWO. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

vwo_create_campaignCreates a campaign in a VWO workspace with the URLs it runs on, its primary URL and at least one goal.
vwo_rename_campaignRenames one VWO campaign.
vwo_add_variationAdds a named variation, with no changes in it, to one VWO campaign.
vwo_create_feature_flagCreates a feature flag in a VWO workspace with its key, type (TEMPORARY or PERMANENT), at least one metric and optional variables.
vwo_update_feature_flagChanges a VWO feature flag's name or description.
vwo_delete_feature_flagPermanently deletes one VWO feature flag with its rules and variables.
vwo_toggle_feature_flagTurns one VWO feature flag on or off in one environment.

Connect it

First connect VWO on Dashboard → Connections, then add Memtro to your client once. The VWO tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared VWO connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What changed in VWO this week?
› Which campaigns are running right now?
› Which websites have no SmartCode detected?
› What conversions and revenue did the checkout report show?
› Rename the homepage hero campaign to Hero banner test.

Questions

Is this an official VWO MCP server?: No. It is Memtro's MCP server with Memtro's VWO connector behind it: the connector reads VWO through its API with the credentials you connect on Dashboard → Connections, and VWO publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in VWO?: Only when you ask, and only what it has been granted: create a campaign (created as not started); rename a campaign; add a variation to a campaign; create a feature flag; update a feature flag's name or description; delete a feature flag; turn a feature flag on or off in an environment. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.