Skip to main content
Claude.ai custom connectors authenticate with OAuth, so you paste a Client ID and Secret instead of a token header.
Available where the Claude / MCP Access settings appear. Requires the MCP surface 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 first-class connector with a consent screen, not a pasted header.
  • You manage one store per set of credentials and want to revoke access per connector.

​
When NOT to use it

  • You use Claude Code or Codex CLI — those accept a token directly. Use the Quickstart and pass your abc_ token as a header (--header in Claude Code, bearer_token_env_var in Codex). The Claude.ai / Claude Desktop connector UI is the only surface that needs OAuth.

​
How it works

You generate an OAuth client bound to your store. When you add the connector, Claude discovers ABConvert’s authorization server, opens a consent screen, and receives an access token scoped to your store. The token is the same abc_ token used elsewhere, so revoking it in Settings cuts access immediately.
  1. You generate a Client ID and Secret in ABConvert.
  2. You paste the MCP URL and credentials into Claude.
  3. Claude runs the OAuth flow (Authorization Code with PKCE) and shows a consent screen.
  4. You approve; Claude stores the token and lists the ABConvert tools.

​
Setup

1

Generate connector credentials

In your Shopify admin, open ABConvert and go to Settings → Claude / MCP Access. In the Claude connector credentials card, click Generate credentials and give it a name (for example, “Claude — Acme store”).You’ll see three values: the Remote MCP server URL, the OAuth Client ID, and the OAuth Client Secret. Copy all three now — the secret is shown once.
Treat the Client Secret like a password. Anyone who has it can obtain an access token for your store. Don’t paste it into shared chats or commit it to a repo.
2

Add the connector in Claude

In Claude, go to Settings → Connectors → Add custom connector.
  • Name: ABConvert
  • Remote MCP server URL: https://mcp.abconvert.io/mcp
Expand Advanced settings and paste:
  • OAuth Client ID: the abcmcp_live_… value
  • OAuth Client Secret: the secret you copied
Click Add.
3

Approve the consent screen

Claude opens a consent page showing which store it’s connecting to. Confirm the store domain is yours and 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 experiments and summarize the results of the top one.”

​
Common mistakes

  • Pasting a token into the Client ID field. The connector fields are an OAuth client identity, not the abc_ access token. Generate credentials from the Claude connector credentials card, not the Access tokens card.
  • Approving a consent screen for the wrong store. The consent page names the store the credentials belong to. If it isn’t yours, cancel and regenerate credentials from the correct store’s admin.
  • Losing the secret. It’s shown once. If you didn’t copy it, revoke the connector and generate a new one.
  • Expecting Claude Code to use these fields. Claude Code and Codex use a token header instead — see the Quickstart.

​
FAQ

Open Settings → Claude / MCP Access, find the connector in the list, and revoke it. Any access token issued through it stops working immediately.
Access tokens are long-lived and stay valid until you revoke the connector. Revoke from Settings to cut access.
Yes. Generate a separate set of credentials from each store’s admin and add each as its own connector in Claude.
Not yet — Codex’s OAuth requires Dynamic Client Registration, which this connector doesn’t offer. Connect Codex with a token instead (bearer_token_env_var in config.toml). See the Quickstart.