{"version":"2.1.287","anchor":"mcp-reconnect-retry-now-tracks-in-flight-servers","canonical_anchor":"mcp-reconnect-retry-now-tracks-in-flight-servers","heading":"MCP server reconnect retries keep track of attempts in progress","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/mcp-reconnect-retry-now-tracks-in-flight-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### MCP server reconnect retries keep track of attempts in progress\n\nClaude Code now tracks which MCP servers already have a reconnect retry running and logs failed retries\n\n**Unclear.** The visible effect of this change on reconnecting MCP servers is not clear.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When a connection to one drops, Claude Code retries it. It now keeps a list of servers that already have a retry in progress, and logs a failed retry as \"retry error\".\n\n**Why**\n\nTracking retries in progress may stop Claude Code from starting overlapping reconnect attempts to the same server.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}