Question 5
Domain 1Your team wants to share a GitHub MCP server configuration so all developers have access to it when they clone the repository. Where should you configure this MCP server?
Correct answer: A
Explanation
GitHub MCP server settings should be stored in the project-level configuration so everyone who clones the repo gets the same setup. The shared file is the project's ".mcp.json" committed to version control, which makes the server available to the whole team instead of only one developer's local machine.
Why each option is right or wrong
A. In the project's .mcp.json file, committed to version control for the team
Project-scoped MCP settings belong in the repository-level configuration file, `.mcp.json`, so they are checked into version control and distributed with every clone. A local user config would only apply to one developer’s machine, whereas the committed project file makes the server definition available to the whole team immediately after checkout.
B. In ~/.claude.json on each developer's machine for personal MCP server configuration
Home-directory config is user-specific and does not automatically propagate through repository cloning.
C. In the root CLAUDE.md file as a structured MCP configuration code block
CLAUDE.md is documentation/instructions, not the canonical machine-readable MCP configuration location.
D. In a .env file at the project root with MCP_SERVER_URL variables defined
.env files hold environment variables, not the structured shared MCP server definition.