docs(mcp): document Claude Code install scopes (local/project/user)#247
Merged
docs(mcp): document Claude Code install scopes (local/project/user)#247
Conversation
The Claude Code sections in `mcp-clients.md` and `integrations/claude-code.md` only showed `-s user` examples plus a project-scope `.mcp.json` block, with no mention of `-s local` — the actual default when `-s` is omitted. Users who wanted a per-project install with private paths/credentials had no documented path; they either committed personal config to `.mcp.json` or dropped everything into user scope. Add a scope-comparison table (storage location, sharing, when to use) plus the precedence order (`local > project > user > plugins > Claude.ai connectors`) so readers can pick the right scope for their situation. Also call out that `project` servers from `.mcp.json` require workspace-trust approval on first use — a relevant safety detail when telling someone to commit a server config to a shared repo. Scopes and storage paths verified against `claude mcp add --help` and the live `~/.claude.json` structure (top-level `mcpServers` for user scope, `projects."<cwd>".mcpServers` for local scope), and cross-checked against https://code.claude.com/docs/en/mcp-configuration.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
local/project/user) to the Claude Code MCP setup sections indocs/guides/mcp-clients.mdanddocs/guides/integrations/claude-code.md, covering storage location, sharing scope, and when to use each.local > project > user > plugins > Claude.ai connectors) and the workspace-trust prompt forprojectservers — both missing from the existing docs.-s localexample so readers know the default scope exists and when to prefer it overprojectoruser.Why
The existing sections only showed
-s usercommands plus a project-scope.mcp.jsonblock, with no mention of-s local— which is actually the default when-sis omitted. A user with a per-project setup containing private paths/credentials had no documented path; they ended up either committing personal config to a shared.mcp.jsonor adding it to user scope and affecting every project.Verification
claude mcp add --help— confirmed--scopeoptions arelocal, user, or projectwithlocalas the default.~/.claude.json— confirmedprojects."<cwd>".mcpServers(local) and top-levelmcpServers(user) are the actual storage shapes.Test plan
ruff check packages/memtomem/srcstill passes (no diff in that tree)