Documentation

Connect ChatGPT

ChatGPT takes the same OAuth path as Claude, not an API key — but a different URL and a different route through the UI. Custom connectors need a paid ChatGPT plan.

  1. Turn on developer mode

    In ChatGPT, open Settings → Connectors → Advanced and switch on Developer mode.

    No toggle there?

    Custom connectors are a paid-plan feature. If the setting is missing, that is why.

  2. Create the connector

    Back on the Connectors screen, press Create, then:

    • Name it anything. “Click Context” works.
    • Leave the connection type on Server URL and paste the URL below.
    • Set authentication to OAuth. Leave the advanced OAuth fields — client ID, secret, scopes — empty. ChatGPT reads them from the server and registers itself.
    • Tick the box confirming ChatGPT has not reviewed this server, then press Create.
    https://app.clickcontext.com/api/mcp/mcp

    Not the Claude URL

    ChatGPT takes the URL literally rather than negotiating a transport, so it needs /api/mcp/mcp. The /api/mcp/sse address that Claude uses will not complete a handshake here.

  3. Enter your connection code

    ChatGPT opens a Click Context page asking for a six-digit code. In your Shopify admin, open Apps → Click Context and press Generate connection code. Codes are single-use and expire after ten minutes.

  4. Ask something

    Using Click Context, where is my biggest conversion leak?
    Which products get traffic but no sales?

    ChatGPT is more literal than Claude about invoking connectors. If it answers from general knowledge instead of your data, name the connector in the prompt.

Differences from Claude

  • Different URL. /api/mcp/mcp, not /api/mcp/sse.
  • Developer mode is required, and with it a paid plan.
  • Connector selection is less automatic. Mentioning Click Context in the prompt reliably triggers it.

Everything past the handshake is identical: same 37 tools, same instruction set, same playbooks.