Wire your testing platform into Claude and the experiment builds itself. Targeting, goals, control, variants, traffic split, preview URLs. You QA, you say "start it," and it's live in minutes instead of waiting days on a designer-to-developer-to-analyst relay.
This is the stage where Claude stops advising and starts doing. Everything before it (the audit, the hypothesis, the variant brief, the sample-size math) produces a spec. This page turns that spec into a live experiment by connecting your A/B testing platform's MCP to Claude.
I run Convert.com as the engine, so that's the worked example. Connect, paste context, instruct, QA, launch.
A connector is either an MCP server (think USB-C for AI) or a CLI. Convert exposes an MCP server, so Claude can create and manage experiments inside Convert directly. It writes the targeting rules, the goals, the control, and the variants, then hands you back preview URLs.
Claude is the brain. The Convert MCP is the hands. Once it's wired in, the instruction "launch this test" reaches all the way into your testing tool and builds the experiment for you.
The catch matters enough that I'll say it twice. Claude builds and previews. You launch. Never let it flip a test live before you've checked both variants render on desktop and mobile.
One command in your terminal wires Convert into Claude:
claude mcp add convert --env CONVERT_API_KEY=YOUR_APPLICATION_ID --env CONVERT_API_SECRET=YOUR_SECRET_KEY --env TOOLS_FOR_CLIENT=all -- npx -y @convertcom/mcp-server@latest
What each piece does:
| Flag | What it is | Where it comes from |
|---|---|---|
CONVERT_API_KEY |
your Convert Application ID | Convert account API settings |
CONVERT_API_SECRET |
your Convert API secret | Convert account API settings |
TOOLS_FOR_CLIENT=all |
exposes the full Convert tool set to Claude | set to all for the complete workflow |
npx -y @convertcom/mcp-server@latest |
runs the official Convert MCP server | pulls the latest published package |
Verify it connected:
claude mcp list
Or run /mcp inside a Claude session. If Convert shows up, the hands are attached.
One dependency lives outside the MCP. Convert tracks behavior through a snippet that has to sit in your store theme, so the Convert tracking script gets pasted into theme.liquid once. That's the only step that touches your Shopify theme, and it's a copy-paste, not a code change. Do it before the first launch and you never think about it again.