{"version":"2.1.227","anchor":"a-failed-mcp-credential-read-no-longer-triggers-a-spurious-r","canonical_anchor":"a-failed-mcp-credential-read-no-longer-triggers-a-spurious-r","heading":"A failed MCP credential read no longer triggers a spurious re-login","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/a-failed-mcp-credential-read-no-longer-triggers-a-spurious-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### A failed MCP credential read no longer triggers a spurious re-login\n\nA failed MCP credential read no longer drags you through a pointless re-login.\n\n**What**\n\nIf reading the stored credentials for an MCP server fails, Claude Code now raises and logs an error instead of behaving as though there were no credentials, which previously would have sent you through authentication again for no reason.\n\n**Evidence**\n\n`Credential store read failed; not reporting credentials as absent`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}