MCP Integration in Claude Code
Last reviewed
Correct answer: B. It reconnects on its own, up to five attempts, with the delay doubling each time.
Explanation
The principle — Transient drops should heal themselves, but not forever, and not at a pace that makes a struggling server worse.
Why the key is correct — If an HTTP or SSE server disconnects mid-session, Claude Code automatically reconnects with exponential backoff: up to five attempts, starting at a one-second delay and doubling each time. After that the server is marked failed and you can retry it yourself.
Why the others are wrong — Manual reconnection is the fallback rather than the first response. The attempts are bounded rather than endless. And the delay widens instead of staying fixed.
Remember this — Five attempts, each waiting twice as long as the last.
Sources — Anthropic's Claude Code MCP reference.
Sources
“If an HTTP or SSE server disconnects mid-session, Claude Code automatically reconnects with exponential backoff: up to five attempts, starting at a one-second delay and doubling each time.”
Practise 10 questions on this topic
Take MCP Integration in Claude Code — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.