Connect Claude Code

Add ShipMCP as an MCP server in Claude Code (the CLI) so your endpoint's tools are available alongside Claude Code's built-in ones.

Quickest path: claude mcp add

From any directory, run:

claude mcp add shipmcp \
  --transport http \
  --url https://mcp.shipmcp.io/<your-slug>/mcp \
  --header "Authorization=Bearer <your-token>"

Replace <your-slug> with your endpoint slug (find it on /endpoints) and <your-token> with a token from the same page. The connection is per-project by default — add --scope user to make it global.

Or edit settings.json directly

Claude Code's config is at ~/.claude.json. Add an entry under mcpServers:

{
  "mcpServers": {
    "shipmcp": {
      "type": "http",
      "url": "https://mcp.shipmcp.io/<your-slug>/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

OAuth instead of static token

Claude Code supports OAuth for HTTP MCP servers — drop the Authorization header from the config and it'll auto-discover via WWW-Authenticate, run Dynamic Client Registration, and walk you through the consent screen on shipmcp.io. See OAuth 2.0 for the protocol details.

Verifying

In Claude Code, run /mcp — your shipmcp entry should show up with a green status and a tool count. Ask the agent something that uses your data ("What's in this corpus?") and watch it call list_documents or similar.

Granting write access

For agent writes / ingest tools (Pro+ only), make sure your token was issued with mcp:write scope. If you're using OAuth, that means ticking the "Also grant write access" checkbox on the consent screen. If you're using a static token from the dashboard, those default to mcp scope — you'll need an OAuth-issued token for writes. See Agent writes & ingest.