Claude Code MCP Setup: Where Server Configuration Lives and How Scopes Conflict
Claude Code must know about an MCP server through configuration before it can connect to it. Definitions can be stored at project, user, or local scope, or be provided centrally by an organization, depending on who should use them. A project's shared .mcp.json file can declare a team's server without exposing personal credentials, while local scope keeps individual secrets private to one project. When the same server name appears in several scopes, Claude Code uses the complete entry from the highest-precedence source rather than merging fields. Organization-managed definitions override the other sources when duplicated.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in