# VWO setup for PopMCP Nothing is typed into PopMCP. You click Connect VWO, sign in to VWO (now Wingify), choose a permission level and approve PopMCP, then choose which workspace to connect if you can reach several. PopMCP is already registered with VWO, so there is no developer app, secret or callback URL. An API token from Developers, Tokens in VWO works too, under More options. - Auth: OAuth authorization - Setup time: 1 min - API base URL: https://app.wingify.com/api/v2 - Credentials screen: https://app.wingify.com/#/developers/tokens - Provider docs: https://developers.wingify.com/reference/authentication ## Approval required before this works No one reviews you, but VWO's help centre says its API is only available on the Enterprise plan. A workspace without API access is refused when you connect. - Typical wait: None once your workspace has API access. Otherwise it depends on your VWO contact. - Cost: VWO quotes the Enterprise plan directly. See wingify.com or ask your VWO contact. - Blocked until approved: Everything. PopMCP's connect check reads the workspace and is refused until API access is on. - Works meanwhile: Decide which permission level the AI should have (Browse only reads; Design, Publish and Admin can change things) and which workspace to connect first. ## Before you begin - A VWO account with API access. VWO's help centre says its API is only available on the Enterprise plan - Your role in VWO caps what the AI can do: Browse only reads, Design can create, Publish and Admin can start and stop tests - Pop-up blockers must allow the VWO sign-in window to open - Only if the AI should change anything: an owner or admin in PopMCP to allow write actions ## Get your credentials ### 1. Start the connection from PopMCP Open the VWO connector in PopMCP and click Connect VWO. There are no fields to fill in: no token, no account id and no developer app. ### 2. Sign in to VWO in the pop-up The sign-in window opens on app.wingify.com, because VWO now goes by Wingify. It is the same product and the same login. Sign in with the account the AI should work as. ### 3. Choose the access to grant, and approve VWO asks which account to connect and which permission level to grant. Browse only reads. Design can also create campaigns. Publish and Admin can start and stop tests. Your own role in VWO is the limit. The labels on your screen may differ a little from this picture. ### 4. Choose the workspace in PopMCP Back in PopMCP, pick the workspace this connection is for. With one workspace there is just one row to choose. The connection is locked to it, and a request for another workspace is refused. To work with another, connect it as a second connection. ### 5. Or paste an API token instead Prefer a token? In VWO open Developers, then Tokens, add a token and pick its permission level. In PopMCP open More options, paste it into API token and connect. The token lasts until you revoke it. The insight tools, such as heatmap analysis, need a sign-in rather than a token. Screen: https://app.wingify.com/#/developers/tokens ### 6. Check the connection in PopMCP The VWO card in PopMCP reads Connected, with the workspace name. The everyday tools load at once, and the whole API is one search away. Starting a test and every other change wait until an owner or admin allows write actions in PopMCP. ## Fields PopMCP asks for - How you connect (connectionType): Click Connect VWO, sign in and approve. VWO asks which permission level to grant. If you can reach several workspaces, you choose one next. Your VWO password is never shared with us. - API token (instead of signing in) (apiToken): Only if you prefer not to sign in. Paste it and the sign-in step is skipped. In VWO open Developers, then Tokens, add a token and pick its permission level. It lasts until you revoke it. Stored encrypted. The insight tools, such as heatmap analysis, need a sign-in. ## Scopes requested - admin - publish - design - browse ## Verify The VWO card in PopMCP shows Connected with the workspace name. Asking the AI for the connection profile (`vwo_connection_profile`) names the workspace and how you connected, and asking it to list your running tests (`vwo_find_campaigns`) confirms it can read them. ## Troubleshooting ### The sign-in window never opens Cause: A pop-up blocker is stopping the VWO sign-in window. Fix: Allow pop-ups for PopMCP in your browser and click Connect VWO again. ### "VWO refused access" Cause: VWO lists its API under the Enterprise plan, or your role may not be able to use it. Fix: Check this workspace's plan and your role with your VWO contact, then connect again. ### "VWO did not accept this token" Cause: The token was copied in part or was revoked. Fix: In VWO open Developers, then Tokens, copy the token again or make a new one, and paste it. ### "Your VWO login cannot reach this workspace any more" Cause: The login was removed from the workspace after connecting. Fix: Reconnect with a login that belongs to the workspace, or choose another workspace. ### A change is refused with a 403 Cause: The permission level chosen for this connection, or your role in VWO, does not allow it. Fix: Connect again and choose a higher level, or ask an admin in VWO to raise your role. ### Feature flag tools answer 404 Cause: These tools apply only to workspaces with Feature Experimentation. Fix: Turn on Feature Experimentation in VWO, or use the campaign tools. ### A tool answers 429 Cause: VWO allows one request per second for each token, and asks for at least a minute's wait after going over. Fix: Wait a minute and try again. PopMCP makes requests take turns, so this is rare unless the same token is used elsewhere too. ### "VWO's insight tools did not accept this connection" Cause: This connection was made with a pasted API token, and these tools need a sign-in. Fix: Connect VWO again by signing in. Every other VWO tool is unaffected. --- Source: https://www.docs.popmcp.com/docs/integrations/vwo/