You run the command that adds an MCP server and you do not pass a scope flag. Which scope does the server land in?

Easyclaude-codemcpscopesconfiguration

Last reviewed 21 Aug 2026

Project scope, because the command was run from inside a project directory in the first place.
Local scope, which is the default when the command is run without a scope flag.Correct answer
User scope, because that is the most convenient place and therefore the sensible default choice.
None of them, since the command refuses to proceed until a scope has been named explicitly.

Show answer & explanation

Correct answer: B. Local scope, which is the default when the command is run without a scope flag.

Explanation

The principle — Every server lands in exactly one scope, and if you do not choose one, one is chosen for you.

Why the key is correct — Local scope is the default. That is the narrowest of the three, so a server added without thinking about scope is the least widely available kind you could have created.

Why the others are wrong — User scope is broader and has to be asked for. Project scope writes to a committed file and is never assumed on your behalf. And nothing refuses to proceed; the command succeeds quietly.

Remember this — No scope flag means the narrowest scope, not the most useful one.

Sources — Anthropic's Claude Code MCP reference.

Sources

Primary sourceConnect Claude Code to tools via MCP — Anthropic · accessed 20 Aug 2026
“Local scope is the default.”

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

You run the command that adds an MCP server and you do not pass a scope flag. Which scope does the server land in?

Related questions

You run the command that adds an MCP server and you do not pass a scope flag. Which scope does the server land in?

Related questions