{"version":"2.1.265","anchor":"mcp-oauth-registration-deferred-when-discovery-already-offe","canonical_anchor":"mcp-oauth-registration-deferred-when-discovery-already-offe","heading":"MCP OAuth: registration deferred when discovery already offered it","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/mcp-oauth-registration-deferred-when-discovery-already-offe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP OAuth: registration deferred when discovery already offered it\n\nMCP OAuth login now delays client registration when the server's discovery info already offers it\n\n**What**\n\nWhen Claude Code connects to an MCP (Model Context Protocol) server that uses OAuth login, it now checks the server's discovery metadata for a `registration_endpoint` or support for `client_id_metadata_document_supported`. If either is present, a new `registrationOfferedByDiscovery` flag is set, and if there's no access or refresh token yet, Claude Code defers registering itself as a client until the actual authentication step instead of trying to register right away.\n\n**Why**\n\nPreviously, missing client info could fail immediately; now, if the server's discovery data already offers a way to register, Claude Code waits and lets registration happen at authentication time instead of failing early.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}