claude-desktop-custom-connector-requires-oauth-not-bearer
Claude Desktop Custom Connectors follow MCP spec 2025-03-26 and require OAuth 2.0 Dynamic Client Registration. When Desktop hits a 401 response, it probes /.well-known/oauth-authorization-server, /.well-known/openid-configuration, /oauth/authorize, and /oauth/token — it never sends the request to /mcp with a static Bearer token. Servers protected by static Bearer auth are fundamentally incompatible with Desktop bridging; they must stay on VPS-permanent registration or have a full OAuth server added.
Related
- claude-desktop-custom-connectors-require-oauth2-no-bearer
- claude-desktop-connector-no-static-bearer-auth
- claude-desktop-custom-connectors-require-oauth-dcr-not-beare
- claude-desktop-custom-connectors-require-oauth-20-dcr-static
- mcp-permanent-11-to-7-desktop-bridge-architecture-decision
- permanent-mcp-7-canonical-list-after-desktop-migration
- claude-desktop-oauth-dcr-incompatible-with-bearer-auth
- desktop-custom-connector-requires-oauth2-dcr-not-bearer
- mcp-tool-budget-does-not-auto-update-on-connector-migration
- r-dash-azure-ad-deferred-local-auth-v1-stack
- r-same-local-auth-v1-azure-ad-deferred