{"version":"2.1.265","anchor":"mcp-client-tool-lists-refresh-after-reconnect-with-new-timi","canonical_anchor":"mcp-client-tool-lists-refresh-after-reconnect-with-new-timi","heading":"MCP client tool lists refresh after reconnect, with new timing telemetry","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/mcp-client-tool-lists-refresh-after-reconnect-with-new-timi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP client tool lists refresh after reconnect, with new timing telemetry\n\nMCP tool lists now refresh automatically after a server reconnects\n\n**What**\n\nWhen an MCP (Model Context Protocol) server reconnects, Claude Code now re-fetches that server's list of tools and merges them back into the available tools, tracked through a new pending-refresh set. The code also adds timing markers around the tool setup step to measure how long it takes.\n\n**Why**\n\nThis keeps the available tool list accurate after a reconnect, so tools from a server that dropped and came back are properly refreshed instead of possibly going stale.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}