claude-desktop-custom-connectors-require-oauth-dcr-not-bearer
Claude Desktop Custom Connectors implement OAuth 2.0 Dynamic Client Registration (MCP spec 2025-03-26). When a connector endpoint returns 401, Desktop probes /.well-known/oauth-authorization-server, /oauth/authorize, and /oauth/token — if none respond, connection fails entirely. Static Bearer tokens are never forwarded; the connector never reaches /mcp. Only public (no-auth) or OAuth-enabled MCP servers can be Desktop-bridged.
Related
- claude-desktop-custom-connectors-require-oauth2-no-bearer
- claude-desktop-connector-no-static-bearer-auth
- desktop-connector-migration-gate-add-before-remove
- desktop-bridge-3-of-4-mcp-servers-confirmed-migration-patter
- dual-claude-json-sync-invariant-session-user-determines-acti
- mcp-permanent-11-to-7-desktop-bridge-architecture-decision
- claude-desktop-custom-connector-requires-oauth-not-bearer
- claude-desktop-oauth-dcr-incompatible-with-bearer-auth
- desktop-custom-connector-requires-oauth2-dcr-not-bearer