There are two ways to connect an assistant to the ShipCelero MCP server at https://mcp.shipcelero.com/mcp: signing in through your browser (used by claude.ai and other OAuth-capable clients — nothing to copy), or a personal API key for clients that authenticate with a token, such as Claude Code. Either way the connection is personal to your login — each team member connects their own assistant.

claude.ai (custom connector)

  1. 1In claude.ai, open Settings → Connectors and choose Add custom connector
  2. 2Paste the URL https://mcp.shipcelero.com/mcp — leave client ID and secret empty
  3. 3Add the connector — a ShipCelero window opens asking you to sign in and approve access
  4. 4Review the permissions the assistant should have (read-only ones are pre-selected) and click Approve — ShipCelero tools become available in your conversations
No API key is needed for claude.ai. The connection appears under Settings → MCP API Access → Connected apps in ShipCelero, where you can disconnect it at any time.

Claude Code

Claude Code authenticates with a personal API key. Create one under Settings → MCP API Access first — see MCP API keys and permissions — then add the server, replacing the placeholder with your own key:

claude mcp add --transport http shipcelero https://mcp.shipcelero.com/mcp \
  --header "Authorization: Bearer sc_mcp_live_REPLACE_WITH_YOUR_KEY"

ChatGPT and other MCP clients

Use the same URL, https://mcp.shipcelero.com/mcp. If the client supports OAuth, sign in and approve access when prompted — the same flow as claude.ai. If the client asks for a token or API key instead, create an API key and paste it as the bearer token.

Generic MCP client (JSON configuration, API key)

{
  "mcpServers": {
    "shipcelero": {
      "type": "http",
      "url": "https://mcp.shipcelero.com/mcp",
      "headers": {
        "Authorization": "Bearer sc_mcp_live_REPLACE_WITH_YOUR_KEY"
      }
    }
  }
}

Clients that cannot set an Authorization header can send the key in an X-ShipCelero-MCP-Key header instead.

Treat an API key like a password: never put it in URLs, shared documents, or chat messages. If a key may have leaked, revoke or regenerate it immediately under Settings → MCP API Access. OAuth connections can be removed there too, under Connected apps.

Trying it out

Ask your assistant something like "Show my five most recent ShipCelero shipments" or "How many labels do I have left this month?". If the connection fails, see MCP troubleshooting.