docs(catalog): Catalog MCP — connect from Claude, ChatGPT and LangSmith Fleet (OAuth route, nvm#3460)

[r-marques]

What

products/catalog/mcp.mdx explained the OAuth route as a mechanism but only walked through the API-key path. This adds Connect from your assistant — one tab per assistant, each the click path verified end to end on staging on 2026-09-16 (nevermined-io/nvm-monorepo#3460):

• Claude (claude.ai) — custom connector, no client id/secret, lazy auth: free tools first, inline Connect on the first paid call, consent, automatic retry.
• ChatGPT — Developer mode (paid plan) → Plugins → new with Authentication: OAuth; the ceremony runs at creation; per-call Allow; stable identity.
• LangSmith Fleet — OAuth provider (langsmith-fleet, no secret, ?consent_type=commerce) + Add custom MCP on the mcp.api.<env> host in OAuth 2.1 (Manual); warning about a second Nevermined server with the same tool names (the one thing that went wrong in the verification).
• Any other MCP host — the spec-driven path and when the mcp.api.<env> host is the right one.

Then: the per-environment client allow-list (contact us with the client identity / provider id), what the consent page asks, and what happens when the grant runs out (silent renewal; cap / window / disconnect ⇒ refused, re-consent; revoke under Connections). The quickstart intro now names itself as the API-key route and points OAuth users here. Same page, no nav change.

Draft because

• The page is also touched by docs#404 / docs(auth): self-registering (CIMD) clients get commerce by configuration; connect/details returns clientOrigin #409 / docs(catalog): Commerce MCP — sandbox test merchants, get_service requestShape, pay_service method #411 (all draft until production runs the epic). This rebases on top once they land — different hunks, but same file.
• Two facts in the Fleet tab depend on nevermined-io/argocd#646, which is open: the provider-id scheme (per-workspace ids registered on request — as written — vs a single documented id any workspace can use), and whether the redirects for production are in place. The Fleet tab will be corrected to whichever ships.
• Production enablement itself (nvm#3461) has not been synced yet; publishing this before then would document a refusal.

mintlify broken-links green — verified against a planted broken link first.

🤖 Generated with Claude Code