If you already work in Claude, ChatGPT, or Cursor, you know the friction. You want to ask about last quarter’s tests, or spin up a new A/B test, and the assistant can’t see any of it. So you open Wingify in another tab, copy the numbers across, paste them back, and lose the thread of the conversation you were having.
The Wingify MCP server removes that step. It connects your AI assistant directly to your Wingify data and actions, so the tools you already use can read your experiments and act on them.

What is MCP?
MCP stands for Model Context Protocol. It’s the standard way for connecting AI tools or AI assistants to outside tools and data. Wingify’s MCP server is that connection for your experimentation platform. Your assistant brings the intelligence, and Wingify brings the data and the actions.
Think of the difference between an app and a website. A dedicated app can do more and is more deeply integrated. A website is a URL you open instantly, with nothing to install. MCP is the URL. There is no new interface to learn and no new prompting style to master because you keep working in the assistant you already know.
What you can do with it
Once you are connected, you can ask your assistant to:
- Create an A/B test or a split URL test
- Pull the report for a test, including segmentation
- Fetch session recordings and heatmaps
- Read behavioral insights
- Create a feature flag in Wingify and push the code into your codebase
That last item matters. A single connection covers the whole loop of analyzing, testing, and shipping, instead of one tool for analytics and another for releases.
Questions you can ask on day one
The fastest way to see the value is to try it on work you are already doing:
- “Create an A/B test on the pricing page with two variations.”
- “How did last month’s checkout test perform, broken down by segment?”
- “Pull the session recordings from the test that just finished.”
- “Pause the campaign that is underperforming.”
Each of those replaces a manual trip into the platform with a single sentence.
Works with the assistants you already use
Claude, ChatGPT, and Cursor have native, one-click connectors. Gemini Enterprise and Microsoft Copilot Studio are supported with a short setup. For anything else, you can use the MCP URL directly.
Context that carries over
A common question is whether you lose your history when you move into an assistant. You don’t. If you ran and analyzed a test through Claude, Claude remembers it and can build on it later. Plus, upon request, your assistant can retrieve previous tests and historical insights. straight from Wingify and factor them into its analysis.
What still lives inside Wingz
MCP complements Wingz, Wingify’s AI layer, rather than replacing it. Three capabilities remain exclusive to the platform: Synthetic A/B testing, IDEA AI, which is Wingify’s proprietary approach to generating test ideas, and Workflows.
Furthermore, Wingz shares the exact same MCP control plane as your assistant. There is no separate system behind the scenes, so what you can do from Claude uses the same actions the platform uses.
Who it’s for
The MCP server is built for teams that have already made AI part of how they work. Whether your organization is driving a mandate to automate processes through AI or your team simply lives in Claude or ChatGPT all day, MCP meets you where you are instead of asking you to learn another interface.
Getting started
The MCP server is available on both the Core and Advanced plans. Core includes a monthly limit on tool calls, while Advanced raises that limit significantly and adds behavioral insights and heatmap data through MCP.
Connect your assistant, ask your first question, and stop copying and pasting between tabs. Start your free trial today or request a demo for more information!






