Skip to main content
Connect ABConvert through Claude’s connector directory on desktop or web. You do not need to create, copy, or store a Client ID or Client Secret.
If the Integrations Hub is enabled, open Integrations → MCP. Otherwise, open Settings → MCP & API Access. Both surfaces require MCP to be enabled for your store — see Overview.

​
When to use it

  • You use Claude.ai on the web, desktop, or mobile and want to drive ABConvert from chat.
  • You want ABConvert to appear as a connector with an OAuth consent screen instead of configuring a token header.
  • You want to connect a specific store through a short-lived code you generate in that store’s ABConvert settings.

​
When NOT to use it

  • You use Claude Code or another header-based MCP client — use an API token from the Quickstart instead.

​
How it works

  1. You choose ABConvert in Claude’s connector directory; Claude discovers the OAuth configuration automatically.
  2. You generate a one-time connect code in the ABConvert settings for the store you want to use.
  3. Claude opens ABConvert’s authorization page, where you enter the connect code and approve access.
  4. Claude receives a store-scoped, expiring OAuth access token and lists the ABConvert tools.

​
Setup

1

Add the connector in Claude

Open Claude’s connector directory, search for ABConvert, and choose Connect.In ABConvert, open Integrations → MCP when the Integrations Hub is enabled, then select Claude → Desktop / web for the same instructions. Legacy Settings uses a direct Generate a Connect Code card instead.
2

Generate a connect code in ABConvert

In your Shopify admin, open ABConvert. If the Integrations Hub is enabled, go to Integrations → MCP, select Claude → Desktop / web, and click Generate connect code under 2. Authorize This Store. Otherwise, go to Settings → MCP & API Access and click Generate connect code in the Generate a Connect Code card.The code is short-lived and connects only the store where you generated it. Keep it private until you enter it in the authorization page.
3

Enter the code and approve access

Claude opens ABConvert’s authorization page. Enter the connect code, confirm the store domain shown on the consent screen is yours, then click Approve.Claude finishes the connection and lists the ABConvert tools.
4

Run your first prompt

Ask Claude to work with your tests:
“List my active ABConvert tests and summarize the results of the top one.”

​
Common mistakes

  • Entering an API token in OAuth fields. URL-based Claude connectors use OAuth discovery and the connect-code page. Use an API token only with a header-based client such as Claude Code.
  • Using an expired or already used connect code. In the Integrations Hub, use Integrations → MCP → Claude → Desktop / web, then click Generate connect code under 2. Authorize This Store. In legacy Settings, use Settings → MCP & API Access and the Generate a Connect Code card. Restart the authorization flow.
  • Approving a consent screen for the wrong store. Cancel, generate a code from the intended store, and connect again.
  • Confusing an API token with a connect code. The Quickstart documents a manual bearer-token setup for Claude Code. That is a separate setup path.

​
FAQ

Disconnect ABConvert in Claude’s connector settings to stop using the connection there. Access-token expiry alone does not revoke an OAuth connection because refresh tokens can renew access. Contact ABConvert support if you need server-side OAuth access revoked, including after a suspected leak. For a manually configured bearer token, use Integrations → MCP → Claude → Claude Code → Manage access tokens in the Integrations Hub. In legacy Settings, use Settings → MCP & API Access and the Access tokens card.
Yes. Add or authorize each store separately and enter a newly generated connect code for that store.
Use a token with Codex unless its connector surface supports the ABConvert URL-only OAuth flow. See the Quickstart.

​
Manual URL setup and CIMD

If you add a custom connector, use https://mcp.abconvert.io/mcp. Choose Claude’s published identity if asked; you do not need to supply your own Client ID or Client Secret. Then complete the same connect-code authorization. ABConvert supports Client ID Metadata Documents (CIMD), which let a compatible OAuth client identify itself using published metadata. OAuth uses PKCE, issues an expiring access token, and supports token refresh. The connector sends that access token as a bearer token automatically. CIMD is not a code or credential you need to copy. See Claude’s connector instructions for current directory and custom-connector controls.