MCP Integration in Claude Code
Last reviewed
Correct answer: A. It refreshes the stored token, reconnects to the server, and retries the request once.
Explanation
The principle — Routine expiry should not surface as a failure, but a genuine credential problem should surface immediately rather than being retried forever.
Why the key is correct — When a request to a server you already signed in to returns 401 Unauthorized, Claude Code refreshes the stored token, reconnects, and retries the request once. One retry is enough to cover expiry, and no more than that.
Why the others are wrong — A browser sign-in is not needed for ordinary expiry. The call is not abandoned; it is retried as part of the recovery. And the retry does not loop, because a second failure means something a retry cannot fix.
Remember this — Refresh, reconnect, retry once — then it tells you.
Sources — Anthropic's Claude Code MCP reference.
Sources
“When a request to an OAuth server you already signed in to returns 401 Unauthorized, Claude Code refreshes the stored token, reconnects, and retries the request once.”
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.