{"version":"2.1.242","anchor":"mcp-servers-reconnect-automatically-when-the-connection-drop","canonical_anchor":"mcp-servers-reconnect-automatically-when-the-connection-drop","heading":"MCP servers reconnect automatically when the connection drops","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/mcp-servers-reconnect-automatically-when-the-connection-drop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### MCP servers reconnect automatically when the connection drops\n\nDropped MCP connections now retry with backoff, showing attempt counts before being marked failed.\n\n**What**\n\nConnected MCP servers over HTTP or SSE now retry the connection with backoff when the transport closes, showing the server as pending with the current attempt number and the maximum, and marking it failed only after the attempts run out.\n\n**Details**\n\n- Applies only to non-stdio, non-SDK servers; locally spawned stdio servers and in-process SDK servers are unaffected.\n- Pending state carries `reconnectAttempt` and `maxReconnectAttempts`; the terminal failure reads \"Connection closed again while reconnecting\".\n- The watcher is installed unconditionally with no flag, and stands down while another reconnect is already in flight or the run is shutting down.\n\n**Evidence**\n\n`Connection closed again while reconnecting`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}