{"version":"2.1.288","anchor":"mcp-oauth-refresh-retry-and-token-save-backend-name","canonical_anchor":"mcp-oauth-refresh-retry-and-token-save-backend-name","heading":"MCP sign-in retries once after some failed fetches","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/mcp-oauth-refresh-retry-and-token-save-backend-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### MCP sign-in retries once after some failed fetches\n\nSome MCP sign-in fetch failures now trigger one retry instead of failing at once, and saved tokens record where they were stored\n\n**Unclear.** It is not clear what is being fetched or what the extra step before the retry does.\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside servers that add tools. Some of these servers need you to sign in.\n\nDuring MCP sign-in, when a fetch fails and there is no saved copy to fall back on, Claude Code now runs an extra step and tries once more. Before, it reported the failure straight away.\n\nThe result of saving sign-in tokens now also records which storage it used.\n\n**Why**\n\nMCP sign-in may hold up better against brief network or server problems.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}