{"version":"2.1.317","anchor":"mcp-reconcile-now-retains-and-replaces-servers-by-declaring","canonical_anchor":"mcp-reconcile-now-retains-and-replaces-servers-by-declaring","heading":"MCP servers declared in the current folder are kept when servers are rechecked","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-reconcile-now-retains-and-replaces-servers-by-declaring","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### MCP servers declared in the current folder are kept when servers are rechecked\n\nWhen Claude Code rechecks its MCP servers, it now keeps ones declared in the current folder and restarts one whose declaring folder changed\n\n**Unclear.** It is not clear which sessions this recheck behaviour applies to.\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. From time to time Claude Code rechecks its list of MCP servers against the current configuration and decides which to keep and which to replace. That recheck now treats servers by the folder that declared them:\n\n- Servers declared in the current folder are kept, just as servers that come from plugins already were.\n\n- A server is replaced when the folder that declares it has changed, not only when its configuration has changed.\n\nThe debug log message for a replacement now reads \"config or folder changed, will replace\".\n\n**Why**\n\nServers set up for a particular folder should now stay running through a recheck instead of being dropped. If the folder that declares a server changes, the server is reconnected so it matches the new folder.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}