desktop-custom-connector-requires-oauth2-dcr-not-bearer

Claude Desktop Custom Connectors require OAuth 2.0 Dynamic Client Registration (MCP spec 2025-03-26). When a server returns 401 on /mcp, Desktop tries /.well-known/oauth-authorization-server, /oauth/authorize, /oauth/token — if none respond, it gives ‘You are not connected yet’ and never sends the actual Bearer token. Static Bearer auth is protocol-incompatible with Desktop connectors; only public (no-auth) or OAuth 2.0 servers can be bridged. Servers with static Bearer tokens must stay VPS-permanent.

Related

• claude-desktop-custom-connector-requires-oauth-not-bearer
• claude-desktop-oauth-dcr-incompatible-with-bearer-auth
• claude-desktop-custom-connectors-require-oauth2-no-bearer
• claude-desktop-custom-connectors-require-oauth-dcr-not-beare
• claude-desktop-connector-no-static-bearer-auth
• mcp-tool-budget-does-not-auto-update-on-connector-migration
• r-dash-azure-ad-deferred-local-auth-v1-stack