> ## Documentation Index
> Fetch the complete documentation index at: https://docs.launchmystore.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude.ai Custom Connector

> Connect Claude on the web and mobile to your LaunchMyStore store via OAuth — no token to copy

# Connect Claude (claude.ai) as a Custom Connector

Claude on the web ([claude.ai](https://claude.ai)) and the Claude mobile apps connect to remote MCP servers through **custom connectors**. Unlike Claude Desktop, Claude Code, or Cursor — which authenticate with a bearer token you paste into a config file — claude.ai authenticates with **OAuth 2.0**: you log into your LaunchMyStore admin in the browser and approve the connection once.

LaunchMyStore's MCP server implements the full MCP authorization flow (OAuth 2.0 with PKCE, Dynamic Client Registration, and RFC 8414 / RFC 9728 discovery), so the connection is fully automatic — there is nothing to configure beyond the server URL.

<Note>
  Setting up Claude Desktop, Claude Code, Cursor, or OpenAI Codex instead? Those use a long-lived token — see the [MCP Server overview](/mcp/overview).
</Note>

## Setup

<Steps>
  <Step title="Add the custom connector">
    In Claude, open **Settings → Connectors** and click **Add custom connector**. Paste the server URL:

    ```text theme={null}
    https://api.launchmystore.io/mcp
    ```

    Leave the **Advanced settings** (OAuth Client ID / Client Secret) **empty** — Claude registers itself with the server automatically via Dynamic Client Registration.
  </Step>

  <Step title="Connect and authorize">
    Click **Add**, then **Connect**. Claude opens a LaunchMyStore login page in a new tab. Sign in with your **merchant account** (the same login you use for the admin dashboard) and click **Authorize** on the consent screen.
  </Step>

  <Step title="Enable tools and start chatting">
    Back in Claude, the connector shows as connected. Open the tools menu in any chat to enable the LaunchMyStore tools you want, then ask away:

    > "Show me this week's sales" · "Create a 10% discount code for the summer collection" · "Which products are low on stock?"
  </Step>
</Steps>

<Warning>
  Only approve the consent screen if **you** initiated the connection from Claude. Approving grants the connector the same store access your admin account has.
</Warning>

## How authorization works

When Claude first contacts the server it receives a `401` response pointing at the server's OAuth discovery documents:

| Endpoint                                  | Purpose                                                                                     |
| ----------------------------------------- | ------------------------------------------------------------------------------------------- |
| `/.well-known/oauth-protected-resource`   | Protected-resource metadata (RFC 9728) — which authorization server protects `/mcp`         |
| `/.well-known/oauth-authorization-server` | Authorization-server metadata (RFC 8414) — authorize / token / registration endpoints       |
| `POST /mcp/oauth/register`                | Dynamic Client Registration (RFC 7591) — Claude registers itself, no pre-shared credentials |
| `GET /mcp/oauth/authorize`                | Authorization endpoint — redirects to the LaunchMyStore login + consent page                |
| `POST /mcp/oauth/token`                   | Token endpoint — exchanges the authorization code (PKCE S256) for an access token           |

The access token issued at the end of the flow is your account's **AI Connector token** — the same credential shown in **Settings → AI Connector (MCP)**.

## Revoking access

Go to **Settings → AI Connector (MCP)** in your admin and click **Revoke & regenerate**. This invalidates every MCP credential at once — claude.ai connectors **and** any desktop clients using the pasted token. To reconnect claude.ai afterwards, open the connector in **Settings → Connectors** and click **Connect** again.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Claude says the connector failed to connect">
    Verify the URL is exactly `https://api.launchmystore.io/mcp` (no trailing slash, no `/sse`). Custom connectors use the Streamable HTTP transport, not the legacy SSE endpoint.
  </Accordion>

  <Accordion title="The login page opens but I land on the dashboard instead of a consent screen">
    You were already signed in and the consent screen was skipped by a stale redirect. Go back to Claude and click **Connect** on the connector again — the consent screen appears once you're authenticated.
  </Accordion>

  <Accordion title="The connector worked before but now every tool call fails">
    The token was likely revoked (Revoke & regenerate in the admin, or a password change). Open **Settings → Connectors** in Claude and click **Connect** on the connector to re-authorize.
  </Accordion>

  <Accordion title="I entered an OAuth Client ID/Secret and the connection fails">
    Remove them. LaunchMyStore uses Dynamic Client Registration — Claude must register itself. Pre-filled credentials from another service will be rejected.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="MCP Server Overview" icon="server" href="/mcp/overview">
    Token-based setup for Claude Desktop, Claude Code, Cursor, and Codex
  </Card>

  <Card title="MCP Tools Reference" icon="wrench" href="/mcp/tools">
    Every tool the connector exposes, with parameters
  </Card>
</CardGroup>