Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
VWO (BYOK) icon

VWO (BYOK)

Read your VWO experimentation setup: feature flags and their rules, projects and environments, websites, A/B campaigns and variations, with your own API token

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderVWOunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which VWO feature flags exist in my main workspace?
Tools called
list_feature_flags
What variables does the VWO flag new_checkout have?
Tools called
get_feature_flag
Which VWO projects and environments do I have?
Tools called
list_flag_projects_and_environments
What targeting rules does the VWO flag new_checkout have in production?
Tools called
list_flag_rules
Show rule 1 of the VWO flag new_checkout in production
Tools called
get_flag_rule
Which websites are set up in VWO and are they sending data?
Tools called
list_websites

About

VWO (BYOK) lets an AI assistant read your own VWO data through the VWO API with a key you supply (VWO API token). Read-only: 9 tools (list_feature_flags, get_feature_flag, list_flag_projects_and_environments, list_flag_rules, get_flag_rule, list_websites, get_website, get_campaign, list_campaign_variations). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.wingify.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by VWO. VWO and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the VWO API (app.wingify.com) with a BYOK key; documentation: https://developers.wingify.com/reference/fme-feature-flags-api. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List feature flagsList the feature flags of a workspace.
  • Get feature flagGet one feature flag by id or key: name, type, variables with defaults, variations, goals and rule count (field list from the VWO resource…
  • List flag projects and environmentsList the feature-experimentation projects and their environments of a workspace, to find environment ids for rule lookups.
  • List flag rulesList the targeting rules of one feature flag in one environment.
  • Get flag ruleGet one targeting rule of a feature flag in an environment.
  • List websitesList the websites (and apps) connected to the workspace with domain, platform, archive state and tracking status.
  • Get websiteGet one website by id: domain, platform, archive and registration state, subdomain tracking and tracking status.
  • Get campaignGet one A/B or other test campaign: type, status, traffic share, device, primary URL, thresholds and result statistics.
  • List campaign variationsList the variations of a campaign with control flag, disabled flag and traffic split.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-vwo.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-vwo.connectorbay.com/mcp
RESTPOST https://byok-vwo.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-vwo.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your VWO API token in the X-Upstream-Key header (get one at developers.wingify.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

VWO connector: questions and answers

What is the VWO connector?

VWO (BYOK) lets an AI assistant read your own VWO data through the VWO API with a key you supply (VWO API token). It is a hosted MCP server with 9 tools such as List feature flags, Get feature flag, List flag projects and environments, List flag rules, Get flag rule, List websites, published by Unify Dynamics LLC. It is independent and not affiliated with VWO.

How do I connect VWO to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-vwo.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-vwo.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-vwo.json.

Do I need a VWO account or API key?

Yes: this is a bring-your-own-key connector. Create a VWO API token at https://developers.wingify.com/reference/authentication and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is VWO read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the VWO connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Supabase Database Config (BYOK)

Read the Postgres settings, connection pooler, disk, backups, upgrade eligibility, SSL enforcement and network restrictions of your Supabase projects with your own personal access token

Live · MCP + REST12 tools

Supabase Project Ops (BYOK)

Read Supabase organization projects and entitlements, regions, add-ons, upgrade and restore status, branches, function details and performance advisors with your own token

Live · MCP + REST10 tools

Supabase Service Config (BYOK)

Read the Auth, REST API, Realtime, Storage, custom domain, SSO and signing key settings and service health of your Supabase projects with your own personal access token

Live · MCP + REST12 tools

Supermemory (BYOK)

Read the documents, extracted memories, connections and settings of your Supermemory organization with your own API key

Live · MCP + REST9 tools

Svix (BYOK)

Read your Svix webhook applications, endpoints, messages, delivery attempts, event types and endpoint stats with your own API key

Live · MCP + REST10 tools

Swarmia (BYOK)

Read your Swarmia engineering metrics (code review, DORA, AI assistant adoption, custom reports) and team list with your own API token

Live · MCP + REST5 tools

Documentation

Back to top

VWO (BYOK) — connector documentation

  • MCP endpoint: https://byok-vwo.connectorbay.com/mcp
  • REST API: POST https://byok-vwo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-vwo.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own VWO VWO API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-vwo.connectorbay.com/health · Tool schemas: https://byok-vwo.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-vwo · agent@connectorbay.com

What VWO (BYOK) is for

VWO (BYOK) lets an AI assistant read your own VWO data through the VWO API with a key you supply (VWO API token). Read-only: 9 tools (list_feature_flags, get_feature_flag, list_flag_projects_and_environments, list_flag_rules, get_flag_rule, list_websites, get_website, get_campaign, list_campaign_variations). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.wingify.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by VWO. VWO and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which VWO feature flags exist in my main workspace?"
  • "What variables does the VWO flag new_checkout have?"
  • "Which VWO projects and environments do I have?"
  • "What targeting rules does the VWO flag new_checkout have in production?"
  • "Show rule 1 of the VWO flag new_checkout in production"
  • "Which websites are set up in VWO and are they sending data?"

What it does

  • list_feature_flags: List the feature flags of a workspace. The VWO docs do not describe the answer fields, so the raw answer is returned.
  • get_feature_flag: Get one feature flag by id or key: name, type, variables with defaults, variations, goals and rule count (field list from the VWO resource description).
  • list_flag_projects_and_environments: List the feature-experimentation projects and their environments of a workspace, to find environment ids for rule lookups.
  • list_flag_rules: List the targeting rules of one feature flag in one environment.
  • get_flag_rule: Get one targeting rule of a feature flag in an environment.
  • list_websites: List the websites (and apps) connected to the workspace with domain, platform, archive state and tracking status.
  • get_website: Get one website by id: domain, platform, archive and registration state, subdomain tracking and tracking status.
  • get_campaign: Get one A/B or other test campaign: type, status, traffic share, device, primary URL, thresholds and result statistics.
  • list_campaign_variations: List the variations of a campaign with control flag, disabled flag and traffic split.

BYOK key

You bring your own VWO VWO API token (https://developers.wingify.com/reference/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to app.wingify.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the VWO API (app.wingify.com) with a BYOK key; documentation: https://developers.wingify.com/reference/fme-feature-flags-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by VWO. VWO and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your VWO account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

VWO (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What VWO (BYOK) is. VWO (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own VWO data: Read your VWO experimentation setup: feature flags and their rules, projects and environments, websites, A/B campaigns and variations, with your own API token. You bring your own VWO VWO API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one VWO call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to app.wingify.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If VWO rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What VWO receives. The request we make on your behalf, including the key and the arguments, under VWO's own terms and privacy policy. VWO acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer VWO gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your VWO data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. VWO (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at VWO at any time to end all access.

Children. VWO (BYOK) is a general-audience service operated by the adult using the assistant, under VWO's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

VWO (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the VWO (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. VWO (BYOK) provides: Read your VWO experimentation setup: feature flags and their rules, projects and environments, websites, A/B campaigns and variations, with your own API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own VWO credentials and only access data you are allowed to access. VWO's terms apply to your use of VWO; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by VWO. VWO and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data VWO returns, lightly trimmed; it may be incomplete, delayed or changed by VWO. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your VWO account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent VWO's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; VWO may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your VWO key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action VWO takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-vwo

VWO (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. VWO (BYOK) never asks for them.

Get VWO (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own VWO VWO API token. Create one at https://developers.wingify.com/reference/authentication, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to VWO. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with VWO.