Skip to main content
By the end of this guide you’ll have an AI assistant connected to ABConvert and a real draft test created from a single prompt.
1

Choose your connection type

  • Claude.ai / Claude Desktop connector: add the ABConvert URL and authorize it with a one-time connect code. No Client ID or Client Secret is required.
  • Claude Code or another header-based client: mint an API token and send it as an Authorization header.
2

Connect your AI assistant

  1. In Claude, go to Settings → Connectors → Add custom connector. Name it ABConvert and enter the Remote MCP server URL: https://mcp.abconvert.io/mcp.
  2. Leave any optional OAuth Client ID and Client Secret fields blank, then click Add.
  3. In ABConvert, go to Settings → MCP & API Access. In Connect to Claude or ChatGPT, click Generate connect code.
  4. When Claude opens the ABConvert authorization page, enter that code, check the store domain, and approve access.
Claude lists the ABConvert tools as soon as the connection completes — no restart needed. See Claude.ai connector for troubleshooting.
3

Confirm the connection

Open a new chat and type:
“Use the ABConvert ping tool”
You should see the assistant call ping and respond with { ok: true }. If a URL-only connector cannot authorize, generate a new connect code and restart that connector’s authorization flow. If a header-based client sees 401, mint or select the correct token. If you see “MCP is not enabled for this shop,” ask ABConvert support to enable the feature for your store.
4

Run your first real prompt

Try one of these:

Price test

“Test 10% off my best-selling product”

Shipping test

“Test free shipping over $50 for US visitors”

Compare results

“How is my snowboard price test doing?”

URL redirect

“Send 50% of /products/old-hoodie traffic to /products/new-hoodie”
The assistant asks for a hypothesis, primary metric, and traffic split before creating anything. Once you confirm, the test lands in your dashboard as a draft — you can review it, then launch from the dashboard or by saying “launch it” in the chat.

​
You’re done

That’s the full setup. Everything else is just exploration — see What you can do for the full surface.

​
Token management

  • One token per header-based app. Mint a separate token for Claude Code, OpenClaw, and every other header-based client. You can revoke one without breaking the others.
  • OAuth connectors use connect codes. Claude connectors added by URL do not use merchant-generated Client IDs or Client Secrets. Generate a new connect code for each authorization attempt.
  • Revoke tokens at any time. In Settings → MCP & API Access, revoke a token to stop its next request.
  • Tokens are shop-scoped. A token minted for Shop A cannot access Shop B, even if the same person owns both.
See Security & token management for the full guide.