Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt

Use this file to discover all available pages before exploring further.

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

Mint an API token

Open ABConvert in your Shopify admin. Go to Settings → Claude / MCP Access and click Generate token.
The Claude / MCP Access settings card with a Generate token button and a list of issued access tokens.
Give the token a name that identifies which app will use it (e.g. “Claude Desktop” or “Jeff’s laptop”) — when you revoke a token later, the name is how you’ll know which one to kill without disrupting other integrations.Copy the token. It starts with abc_ and you can only view it once — paste it somewhere safe immediately.
Treat the token like a password. Anyone who has it can create, modify, and delete tests on your store. Don’t paste it in shared chats or commit it to a repo.
2

Connect your AI assistant

Pick the assistant you use:
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows).Add ABConvert to the mcpServers block:
{
  "mcpServers": {
    "abconvert": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.abconvert.io/mcp",
        "--header",
        "Authorization: Bearer abc_your_token_here"
      ]
    }
  }
}
Claude Desktop’s config file only supports stdio-based MCP servers (command + args). The npx mcp-remote … shim bridges to ABConvert’s HTTP endpoint. Configs that use "url" and "headers" directly (Cursor / VS Code style) are silently ignored by Claude Desktop.
Save the file. Quit and re-open Claude Desktop (Cmd+Q, not just close the window).
If Claude Desktop logs show spawn npx ENOENT, replace "command": "npx" with the absolute path to your npx binary (find it with which npx). Claude Desktop’s spawn environment doesn’t always inherit your shell PATH.
3

Confirm the connection

Open a new chat and type:
“Use the ABConvert ping tool”
You should see Claude call ping and respond with { ok: true }. If you see a 401, the token is wrong or revoked — re-mint and try again. If you see “MCP is not enabled for this shop,” ask ABConvert support to flip the enable-mcp feature flag for you.
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”
Claude will ask 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, then launch from the dashboard or by saying “launch it” in the chat.
Tests default to draft for safety. To skip the draft step, say something explicit like “launch it immediately” or “go live now” in your prompt.

​
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 app. Mint a separate token for Claude Desktop, Claude Code, OpenClaw, etc. When you replace your laptop or stop using one tool, you can revoke just that token without breaking the others.
  • Revoke at any time. Settings → Claude / MCP Access → Revoke. Takes effect within seconds — the next call from that token returns 401.
  • Tokens are shop-scoped. A token you mint for Shop A cannot be used to access Shop B, even if the same person owns both.
See Security & token management for the full guide.