claude-desktop-custom-connectors-require-oauth2-no-bearer

Claude Desktop Custom Connectors do NOT support static Bearer token authentication. When a server returns 401, Desktop attempts OAuth 2.0 Dynamic Client Registration by probing /.well-known/oauth-authorization-server, /.well-known/openid-configuration, /oauth/authorize, /oauth/token — if none respond, connection fails with ‘You are not connected yet’. It never sends the Bearer header to the actual MCP endpoint. Only public (no-auth) servers or full OAuth 2.0 servers can be added as Desktop connectors.

Related

• claude-desktop-connector-no-static-bearer-auth
• docker
• dual-claude-json-sync-invariant-session-user-determines-acti
• desktop-connector-migration-gate-add-before-remove
• mcp-bearer-token-must-live-in-claude-json-headers-not-url
• claude-desktop-custom-connectors-require-oauth-dcr-not-beare
• 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