A developer adds a remote MCP server with claude mcp add and no --scope flag. Where is the server available afterwards?
id q26dec6d683
Home / Claude Certified Architect – Foundations / Objective 2.4
Domain 2: Tool Design & MCP Integration · 18% of the exam · Full exam outline
MCP server scoping: project-level (.mcp.json) for shared team tooling vs user-level (~/.claude.json) for personal/experimental servers. Environment variable expansion in .mcp.json (e.g., ${GITHUB_TOKEN}) for credential management without committing secrets. That tools from all configured MCP servers are discovered at connection time and available simultaneously to the agent. MCP resources as a mechanism for exposing content catalogs (e.g., issue summaries, documentation hierarchies, database schemas) to reduce exploratory tool calls. Configuring shared MCP servers in project-scoped .mcp.json with environment variable expansion for authentication tokens. Configuring personal/experimental MCP servers in user-scoped ~/.claude.json. Enhancing MCP tool descriptions to explain capabilities and outputs in detail, preventing the agent from preferring built-in tools (like Grep) over more capable MCP tools. Choosing existing community MCP servers over custom implementations for standard integrations (e.g., Jira), reserving custom servers for team-specific workflows. Exposing content catalogs as MCP resources to give agents visibility into available data without requiring exploratory tool calls.
A developer adds a remote MCP server with claude mcp add and no --scope flag. Where is the server available afterwards?
id q26dec6d683
A team wants everyone who clones its repository to get the same MCP server for the shared issue tracker. Which scope should they add the server with?
id q4082e80d92