{"version":"2.1.317","anchor":"mcp-lazy-connect-adoption-clears-stale-cache-when-it-fails","canonical_anchor":"mcp-lazy-connect-adoption-clears-stale-cache-when-it-fails","heading":"MCP servers that fail to reconnect no longer stay stuck on stale saved state","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-lazy-connect-adoption-clears-stale-cache-when-it-fails","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### MCP servers that fail to reconnect no longer stay stuck on stale saved state\n\nWhen a saved or sign-in-needed MCP server fails after connecting on demand, Claude Code now clears its saved state instead of only logging a warning\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Claude Code can wait to connect to one until it is needed. When a server that was saved from earlier, or one waiting for you to sign in, fails to be picked up after such a connection, Claude Code now clears its saved state for that server. Before, it only logged a warning.\n\nServers waiting for sign-in can also be picked up in more cases, and their saved sign-in entry is removed once they connect.\n\n**Why**\n\nThis is likely to fix MCP servers that stayed stuck showing an old saved state or a sign-in request.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}