{"version":"2.1.323","anchor":"mcp-server-unregisteredremoved-states-and-revoked-tool-hand","canonical_anchor":"mcp-server-unregisteredremoved-states-and-revoked-tool-hand","heading":"Removed MCP servers are now held like reconnecting ones","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-server-unregisteredremoved-states-and-revoked-tool-hand","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Removed MCP servers are now held like reconnecting ones\n\nClaude Code now treats a removed MCP server the same way as one that is reconnecting, and counts tools from servers not yet registered in remote sessions\n\n**Unclear.** What a reader sees when a removed server's tools are held is not stated.\n\n**What**\n\nAn MCP server is an outside program that gives Claude Code extra tools. Claude Code already put a server's tools on hold while that server was reconnecting. A server that has been removed is now put on hold the same way.\n\nIn remote sessions, Claude Code also now counts the tools that belong to MCP servers which have not finished registering yet, and reports that count in its usage data.\n\n**Why**\n\nThis affects how tools from MCP servers that connect late, or go away, are treated in remote sessions.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}