> ## 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.

# Connect Claude to ABConvert in 5 minutes

> Connect your AI assistant — OAuth connector credentials for Claude Desktop and Claude.ai, an API token for Claude Code and other clients — and run your first test prompt in five minutes.

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.

<Steps>
  <Step title="Mint an API token">
    <Note>
      Using **Claude Desktop or Claude.ai**? Skip this step — they connect with OAuth connector credentials you'll generate in step 2. The token below is for Claude Code and other header-based clients.
    </Note>

    Open ABConvert in your Shopify admin. Go to **Settings → Claude / MCP Access** and click **Generate token**.

    Give the token a name that identifies which app will use it (e.g. "Claude Code" 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.

    <Warning>
      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.
    </Warning>
  </Step>

  <Step title="Connect your AI assistant">
    Pick the assistant you use:

    <Tabs>
      <Tab title="Claude Desktop / Claude.ai">
        Claude Desktop connects through a custom connector with OAuth — no config file, no token header. The same flow works on Claude.ai web and mobile.

        1. In ABConvert, go to **Settings → Claude / MCP Access**. In the **Claude connector credentials** card, click **Generate credentials** and give it a name. Copy all three values — the client secret is shown once.

        <Frame>
          <img src="https://mintcdn.com/abconvert/la5DLsY6Jt3D_H0z/images/mcp/claude-connector-credentials-modal.png?fit=max&auto=format&n=la5DLsY6Jt3D_H0z&q=85&s=950b12483e15ef3e41662ee2d654d0da" alt="The Generate connector credentials modal showing the remote MCP server URL, an OAuth client ID, and an OAuth client secret, each with a copy button." width="620" height="495" data-path="images/mcp/claude-connector-credentials-modal.png" />
        </Frame>

        2. In Claude, go to **Settings → Connectors → Add custom connector**. Name it `ABConvert` and paste the **Remote MCP server URL** (`https://mcp.abconvert.io/mcp`).

        3. Expand **Advanced settings**, paste the **OAuth Client ID** and **OAuth Client Secret**, and click **Add**.

        4. Approve the consent screen. Check that the store domain it names is yours.

        Claude lists the ABConvert tools as soon as the connector is added — no restart needed.

        See [Claude.ai connector](/mcp/claude-connector) for common mistakes and how to revoke access.
      </Tab>

      <Tab title="Claude Code (CLI)">
        Run one command:

        ```sh theme={null}
        claude mcp add --transport http abconvert https://mcp.abconvert.io/mcp \
          --header "Authorization: Bearer abc_your_token_here"
        ```

        That's it. The next chat session will have the ABConvert tools available.

        Verify it's connected:

        ```sh theme={null}
        claude mcp list
        # Should show: abconvert (http) — Connected
        ```
      </Tab>

      <Tab title="OpenClaw / other MCP clients">
        Most MCP-aware clients accept an HTTP transport URL plus an Authorization header. Use:

        * **URL:** `https://mcp.abconvert.io/mcp`
        * **Header:** `Authorization: Bearer abc_your_token_here`

        Refer to your client's MCP setup docs for the exact config format.
      </Tab>
    </Tabs>
  </Step>

  <Step title="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, your credential is wrong or revoked — re-mint the token (or regenerate connector credentials and re-add the connector) 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.
  </Step>

  <Step title="Run your first real prompt">
    Try one of these:

    <CardGroup cols={2}>
      <Card title="Price test">
        > "Test 10% off my best-selling product"
      </Card>

      <Card title="Shipping test">
        > "Test free shipping over \$50 for US visitors"
      </Card>

      <Card title="Compare results">
        > "How is my snowboard price test doing?"
      </Card>

      <Card title="URL redirect">
        > "Send 50% of /products/old-hoodie traffic to /products/new-hoodie"
      </Card>
    </CardGroup>

    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.

    <Tip>
      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.
    </Tip>
  </Step>
</Steps>

## You're done

That's the full setup. Everything else is just exploration — see [What you can do](/mcp/tools) for the full surface.

## Token management

* **One token per app.** Mint a separate token for Claude Code, OpenClaw, and every other header-based client. When you replace your laptop or stop using one tool, you can revoke just that token without breaking the others.
* **Connector credentials are separate.** Claude Desktop and Claude.ai authenticate with OAuth connector credentials, not tokens. Revoke them from the same **Settings → Claude / MCP Access** page.
* **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](/mcp/security) for the full guide.