{"version":"2.1.221","anchor":"disabling-an-mcp-server-mid-session-unloads-its-tools-comman","canonical_anchor":"disabling-an-mcp-server-mid-session-unloads-its-tools-comman","heading":"Disabling an MCP server mid-session unloads its tools, commands and resources","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/disabling-an-mcp-server-mid-session-unloads-its-tools-comman","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Disabling an MCP server mid-session unloads its tools, commands and resources\n\nDisabling an MCP server mid-session now actually removes its tools, commands and resources.\n\n**What**\n\nA server that becomes disabled while Claude Code is running is now fully torn down instead of leaving its capabilities loaded.\n\n**Details**\n\n- New branch in the MCP state reducer for servers that have become disabled.\n- It tears down the connection, drops the per-server refresh subscriptions, and rewrites the client entry to `type: \"disabled\"`.\n- That server's tools, commands, resources and resource templates are filtered out of app state.\n- Policy-blocked servers are handled on a separate path, which now also covers cache-backed clients.\n\n**Evidence**\n\n`{ name: z.name, type: \"disabled\", config: z.config }`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}