MCP Integration in Claude Code
Last reviewed
Correct answer: C. Project scope, because it writes a file at the project root that you then commit to version control.
Explanation
The principle — Sharing a server is a version-control act, not an account setting.
Why the key is correct — Project-scoped servers enable team collaboration by storing configurations in a file at your project's root directory, and the documentation's advice is to check that file into version control so everyone on your team gets the same MCP tools and services. The repository is the distribution mechanism.
Why the others are wrong — User scope widens which of your projects see a server, not which people do. No team account distributes servers. And nothing lives in the home directory and synchronises; the file that matters is at the project root.
Remember this — If it is not committed, it is not shared.
Sources — Anthropic's Claude Code MCP reference.
Sources
“Project-scoped servers enable team collaboration by storing configurations in a .mcp.json file at your project's root directory.”
“Check .mcp.json into version control so everyone on your team gets the same MCP tools and services.”
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.