{"version":"2.1.314","anchor":"mcp-oauth-401-handling-can-recover-via-the-auth-provider-c","canonical_anchor":"mcp-oauth-401-handling-can-recover-via-the-auth-provider-c","heading":"MCP servers that reject a login get extra recovery steps first","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-oauth-401-handling-can-recover-via-the-auth-provider-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### MCP servers that reject a login get extra recovery steps first\n\nWhen an MCP server answers \"not authorised\", Claude Code now tries two extra steps before marking it as needing you to log in\n\n**What**\n\nAn MCP server is an outside tool server Claude Code connects to. When one answers \"not authorised\" without saying how to log in, Claude Code now runs two extra steps before it marks the server as needing authentication. Clearing its saved login details for that server now happens after those steps. It is skipped if the signed-in identity changed while the connection was being set up.\n\n**Why**\n\nSome MCP servers may now reconnect without asking you to log in again.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}