One definition of a server wins on precedence over another. What happens to the fields in the definition that lost?

Easyclaude-codemcpscopesprecedence

Last reviewed 21 Aug 2026

The incomplete entry is skipped in favour of the complete one, regardless of which scope each came from.
They fill in wherever the winning entry left a field unset, so the two definitions combine into one.
They are discarded entirely, because the winning entry is taken and used as a whole.Correct answer
The headers survive even when the URL does not, because credentials are carried separately from endpoints.

Show answer & explanation

Correct answer: C. They are discarded entirely, because the winning entry is taken and used as a whole.

Explanation

The principle — Precedence selects an entry; it does not assemble one.

Why the key is correct — The entire server entry from the winning source is used, and fields are not merged across scopes. The losing definition contributes nothing at all, including any field the winner happens to lack.

Why the others are wrong — Nothing fills in gaps from the loser. Headers get no special treatment. And a more complete entry does not overtake a less complete one, because completeness is never compared.

Remember this — You get one entry, whole, not the best parts of two.

Sources — Anthropic's Claude Code MCP reference.

Sources

Primary sourceConnect Claude Code to tools via MCP — Anthropic · accessed 20 Aug 2026
“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.

Start the test

One definition of a server wins on precedence over another. What happens to the fields in the definition that lost?

Related questions

One definition of a server wins on precedence over another. What happens to the fields in the definition that lost?

Related questions