Connecting Claude

The shop MCP server speaks Streamable HTTP. Every capability the account may reach becomes a tool, filtered by scope, permission, plan and release ring — so a connection can never offer a tool the underlying action would then refuse.

1. 1Open Settings → Connectors → Add custom connector.
2. 2Paste the shop MCP server URL from the MCP servers page.
3. 3Claude registers itself and opens the Service VIN consent screen. Approve it as the shop owner, or as whichever member you want the connection to act as.

Dynamic client registration means there is nothing to create on our side and no client id to paste. The consent screen names what the connection may do, in the shop's own vocabulary rather than in scope strings.

claude mcp add --transport http servicevin $SERVICEVIN_MCP_URL

claude mcp add --transport http servicevin $SERVICEVIN_MCP_URL \
  --header "Authorization: Bearer $SERVICEVIN_API_KEY"

The OAuth form handles token refresh for you. The header form is right for CI and for anything unattended, where there is nobody to complete a browser flow — mint a key scoped to exactly what that job needs.

From the Messages API, name the server in mcp_servers and supply a token you obtained yourself. Via the API connector Claude uses tools only — prompts and resources are client-side features, so a Desktop or Claude Code connection gets more than an API one does.

{
  "model": "claude-opus-5",
  "max_tokens": 2048,
  "messages": [
    {
      "role": "user",
      "content": "Who is running late today?"
    }
  ],
  "mcp_servers": [
    {
      "type": "url",
      "url": "$SERVICEVIN_MCP_URL",
      "name": "servicevin",
      "authorization_token": "$SERVICEVIN_OAUTH_TOKEN"
    }
  ]
}

The registry is growing past two hundred capabilities, which is a supported shape rather than a problem: enable deferred loading on the toolset and Claude searches the tool list instead of reading it. That is why every capability carries a short summary written as retrieval text and a longer operating contract underneath — the first is what gets it found, the second is what makes it used correctly.