{"version":"2.1.290","anchor":"mcp-driver-errors-skip-cleanup-when-the-abort-reason-is-deli","canonical_anchor":"mcp-driver-errors-skip-cleanup-when-the-abort-reason-is-deli","heading":"Deliberately stopped MCP connections skip their error cleanup","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-driver-errors-skip-cleanup-when-the-abort-reason-is-deli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Deliberately stopped MCP connections skip their error cleanup\n\nWhen an MCP connection is stopped on purpose, Claude Code no longer runs its usual error cleanup for it\n\n**Unclear.** Exactly which deliberate stops are recognized is not clear.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. When an MCP connection hit an error, Claude Code always stopped it and cleaned up. It now skips that step when the connection was stopped deliberately.\n\n**Why**\n\nThis avoids handling the same error twice when a connection is replaced on purpose.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}