MCP Integration in Claude Code
Last reviewed
Correct answer: A. Your local entry won outright and was used whole, so the project entry's header was never applied.
Explanation
The principle — When you override a server, you replace it. You do not amend it.
Why the key is correct — Local scope sits above project scope, so your entry won. The entire server entry from that source is used, and fields are not merged across scopes, so the header defined in the project file played no part. Your corrected URL arrived exactly as you wrote it, which is to say without any authentication.
Why the others are wrong — The two entries never combine. There is no field-level fallback to the losing definition. And nothing warns you that a field was discarded, because from the client's point of view no field was discarded — a different entry was simply chosen.
Remember this — Overriding one field of a server means restating every other field that you still need, and that includes the credentials.
Sources — Anthropic's Claude Code MCP reference.
Sources
“The entire server entry from that source is used; fields are not merged across scopes.”
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.