MCP Integration in Claude Code
Last reviewed
Correct answer: C. It went in at the default scope, which files a server under the one repository you added it from.
Explanation
The principle — A server that is absent and a server that is broken produce different symptoms, and the first question is always which of the two you are looking at.
Why the key is correct — Local-scoped servers are tied to the project where you added them: the repository root, or the exact directory if you were not in a git repository. Local scope is also the default, so any server added without a scope flag behaves this way. Opening a different repository puts you outside the only project the entry was ever filed under.
Why the others are wrong — Corruption would break the server in its original project as well, and there it still works. Availability across the whole machine is user scope's behaviour rather than the default. And an authentication problem leaves the server listed with a status attached to it, instead of removing it from the list.
Remember this — A server missing in one directory and present in another is a scope question before it is anything else.
Sources — Anthropic's Claude Code MCP quickstart.
Sources
“Local-scoped servers are tied to the project where you added them: the repository root, or the exact directory if you weren't in a git repository.”
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.