{"version":"2.1.321","anchor":"mcp-connection-teardowndedup-no-longer-conditional-on-a-fea","canonical_anchor":"mcp-connection-teardowndedup-no-longer-conditional-on-a-fea","heading":"MCP connection cleanup now always runs and reports closed connections","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-connection-teardowndedup-no-longer-conditional-on-a-fea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### MCP connection cleanup now always runs and reports closed connections\n\nMCP connection cleanup and reuse now always run, and a server that closes during discovery is marked failed with a clear reason\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Claude Code keeps track of its connections to them so it can reuse and clean them up. That tracking used to run only when an internal check passed. It now always runs.\n\nIf a server's connection closes while Claude Code is still discovering what the server offers, the server is now marked as failed with the message \"Connection closed during discovery\".\n\n**Why**\n\nThis way of reconnecting to MCP servers is now the normal behaviour, and when a server drops out early you see a reason instead of an unexplained failure.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}