{"version":"2.1.300","anchor":"mcp-auth-failure-classification-still-refused-no-refresh","canonical_anchor":"mcp-auth-failure-classification-still-refused-no-refresh","heading":"Failed MCP re-sign-ins are now sorted into two kinds","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/mcp-auth-failure-classification-still-refused-no-refresh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Failed MCP re-sign-ins are now sorted into two kinds\n\nWhen signing back in to an MCP server fails, Claude Code now records whether it was refused again or had no refresh token\n\n**What**\n\nMCP servers are outside tools you connect to Claude Code, and some need you to sign in. When Claude Code tries to sign back in to one and fails, it now sorts the failure into one of two kinds:\n\n- still refused, when the server turns the sign-in down again\n\n- no refresh token, when there is no saved token to renew the sign-in with\n\n**Why**\n\nThis makes it easier to tell why signing back in to an MCP server failed.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}