{"version":"2.1.309","anchor":"mcp-server-removal-now-returns-early-with-async-cleanup","canonical_anchor":"mcp-server-removal-now-returns-early-with-async-cleanup","heading":"Removing an MCP server can report success before cleanup finishes","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-server-removal-now-returns-early-with-async-cleanup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Removing an MCP server can report success before cleanup finishes\n\nRemoving an MCP server now reports success sooner and only waits for cleanup when the server is cached or connected\n\n**Unclear.** It is not clear what condition controls the discovery-entry removal, so whether a removed server can still appear in discovery is unknown.\n\n**What**\n\nAn MCP server is an outside program that gives Claude Code extra tools. When you remove one, Claude Code now confirms the removal and only waits for cleanup when the server is cached, connected or in one other condition. Removing its discovery entry also now happens only in that other condition. Before, removal always waited for both cleanup steps.\n\n**Why**\n\nThis changes how long MCP server removal takes to report back.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}