{"version":"2.1.287","anchor":"mcp-connection-closed-only-after-in-flight-calls-finish-whe","canonical_anchor":"mcp-connection-closed-only-after-in-flight-calls-finish-whe","heading":"MCP connections wait for running tool calls before closing on a stale cached listing","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/mcp-connection-closed-only-after-in-flight-calls-finish-whe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### MCP connections wait for running tool calls before closing on a stale cached listing\n\nWhen an MCP server's cached tool listing is rejected, Claude Code now waits for running tool calls to finish before closing the connection\n\n**Unclear.** It is not clear exactly which calls and tasks are counted as still using the connection.\n\n**What**\n\nAn MCP server is an outside program that gives Claude Code extra tools. Claude Code can keep a saved copy of what a server offered on an earlier connection and reuse it when it connects again. If that saved copy is rejected after the connection is made, Claude Code closes the connection. Before, it closed it straight away. Now it closes only once no tool call (a single request to use one of the server's tools) and no background task is still using it. The next connection then asks the server directly what it offers.\n\n**Why**\n\nTool calls that were already running on that server are no longer cut off just because the saved listing turned out to be out of date.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}