{"version":"2.1.321","anchor":"mcp-connection-cache-now-always-keeps-pending-connection-tra","canonical_anchor":"mcp-connection-cache-now-always-keeps-pending-connection-tra","heading":"Closing an MCP connection now always checks for one still being set up","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-connection-cache-now-always-keeps-pending-connection-tra","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Closing an MCP connection now always checks for one still being set up\n\nClosing or clearing an MCP connection now always checks for a connection still in progress, where before it only did under one internal condition\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When Claude Code closes or clears a connection to one, it now always checks whether a connection to it is still being set up. Before, it did this only when an internal check passed.\n\n**Why**\n\nWhat used to depend on a condition now happens every time.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}