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, shares the server definition with teammates, but Claude Code still asks each user to approve project-scoped servers before use. This is the right scope for something 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 OG Flow Code Premium Toolkit?
Yes — MCP server scope — project vs. user and patterns like it are covered by the commands, and in higher tiers the specialist agents and guided skills, in OG Flow Code Premium Toolkit. Tiers start at $19.90.
Want the full command, hook, and template pack?
This is one pattern from the OG Flow Code toolkit. Choose the tier that fits your workflow, including Multi-Stack for six additional language stacks.
See pricing — from $19.90 once