{"version":"2.1.246","anchor":"mcp-servers-declared-under-a-previous-workspace-root-are-dro","canonical_anchor":"mcp-servers-declared-under-a-previous-workspace-root-are-dro","heading":"MCP servers declared under a previous workspace root are dropped","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/mcp-servers-declared-under-a-previous-workspace-root-are-dro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### MCP servers declared under a previous workspace root are dropped\n\nMCP servers declared under a different workspace root are now dropped instead of lingering.\n\n**What**\n\nA project- or local-scoped MCP server whose declaring location no longer matches the current workspace root is now marked stale and torn down, along with its tools, commands, resources and prompt templates. Previously only removal or a changed config hash retired a server, so one declared in a different workspace root could linger.\n\n**Evidence**\n\n`excludeStalePluginClients: marking stale (declared under a previous workspace root)`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}