{"version":"2.1.309","anchor":"mcp-tool-removal-reason-replaced","canonical_anchor":"mcp-tool-removal-reason-replaced","heading":"Claude is told when an MCP server's tools were replaced by another server's","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-tool-removal-reason-replaced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude is told when an MCP server's tools were replaced by another server's\n\nWhen an MCP server's tools are replaced by another server's mid-session, Claude is now told which server to use instead\n\n**Unclear.** It is not stated what causes one MCP server's tools to be replaced by another's.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When a server's tools are taken away, Claude Code tells the model why, using reasons such as disabled, switched off or not configured. There is now another reason: the tools were replaced in this session by the tools of a named MCP server, and the model should use those instead.\n\n**Why**\n\nIf one server's tools are swapped for another's partway through a session, Claude knows where the tools went instead of failing to find them.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}