MCP Configuration
MCP server scope — project vs. user
MCP servers can be registered per-project (shared via .mcp.json) or per-user (available in every project you open).
A project-scoped server, defined in a .mcp.json committed to the repo, means every teammate who opens the project gets the same tools automatically — the right choice for anything project-specific, like a server that talks to that project's own API.
A user-scoped server follows you across every project instead, which fits general-purpose tools you want available everywhere regardless of which repo you're in.
Mixing the two is normal: project-specific servers in .mcp.json, personal general-purpose ones registered at the user level.
Check .mcp.json in the project root for anything scoped thereFrequently asked questions
What does MCP server scope — project vs. user do in Claude Code?
MCP servers can be registered per-project (shared via .mcp.json) or per-user (available in every project you open).
How do I use it?
Try: Check .mcp.json in the project root for anything scoped there
Any caveats to know about?
Mixing the two is normal: project-specific servers in .mcp.json, personal general-purpose ones registered at the user level.
Is this covered in the Claude Code Toolkit?
Yes — MCP server scope — project vs. user and patterns like it are part of the full command, hook, and template pack included with a Claude Code Toolkit subscription.
Want the full command, hook, and template pack?
This is one pattern out of the full Claude Code Toolkit — subscribe for the complete set, plus everything we add going forward.
Subscribe to the toolkit — $79/mo