{"version":"2.1.323","anchor":"mcp-oauth-refresh-refusals-with-unhandled-error-codes-rewrit","canonical_anchor":"mcp-oauth-refresh-refusals-with-unhandled-error-codes-rewrit","heading":"MCP servers ask you to sign in again after an unrecognized refresh refusal","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-oauth-refresh-refusals-with-unhandled-error-codes-rewrit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP servers ask you to sign in again after an unrecognized refresh refusal\n\nWhen an MCP server refuses a sign-in refresh with an unrecognized error, Claude Code now asks you to sign in again\n\n**What**\n\nMCP servers (outside tools connected through the Model Context Protocol) that need a login hand Claude Code a token that it renews from time to time. If the server refuses a renewal with an error code the MCP SDK does not know how to handle, and your saved login has not changed since, Claude Code now treats the refusal as one that needs a fresh sign-in and asks you to sign in again.\n\n**Why**\n\nBefore, a refusal like this could leave the MCP server stuck and unusable without telling you to sign 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"}