{"version":"2.1.221","anchor":"mcp-teardown-handles-cached-clients-not-just-connected-ones","canonical_anchor":"mcp-teardown-handles-cached-clients-not-just-connected-ones","heading":"MCP teardown handles cached clients, not just connected ones","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-teardown-handles-cached-clients-not-just-connected-ones","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP teardown handles cached clients, not just connected ones\n\nCached MCP server connections are now cleaned up properly instead of being skipped.\n\n**What**\n\nCleanup paths that previously ignored cache-backed clients now run against them too, so cached server state is properly cleared.\n\n**Details**\n\n- The three disconnect\/cleanup paths in the MCP store moved from `type === \"connected\"` checks to a helper matching `e.type === \"connected\" || e.type === \"cached\"`.\n- `clearServerCache` now runs for cached entries as well.\n- Entries that match neither type are skipped early.\n\n**Evidence**\n\n`clearServerCache`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}