Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
Pick an entry · j / k steps through
1 entry
Changesopen
5 entries
MCP Server Scope Terminology Updateopen
#
What's wrong with this entry?
Anonymous. No account, no email.
The primary change in this version is a renaming of MCP (Model Context Protocol) server scopes to improve clarity:
Scope Renaming#
What's wrong with this entry?
Anonymous. No account, no email.
- "project" → "local": MCP servers that are specific to the current project are now called "local" servers
- "global" → "user": MCP servers available across all projects are now called "user" servers
What This Means for Users#
What's wrong with this entry?
Anonymous. No account, no email.
When managing MCP servers, you'll now see updated terminology:
- Local servers (formerly "project"): Private to you in the current project
- User servers (formerly "global"): Available in all your projects
- Project servers: Shared via .mcp.json (terminology unchanged)
Examples#
What's wrong with this entry?
Anonymous. No account, no email.
When using MCP-related commands, the scope names have changed:
# Adding an MCP server with the new scope names
claude mcp add --scope local # Adds to current project only
claude mcp add --scope user # Adds to all your projects
# The allowed scopes list now shows:
# ["local", "user"] instead of ["user", "global"]Technical Details#
What's wrong with this entry?
Anonymous. No account, no email.
The update includes:
- Updated display strings in the
vjfunction that formats scope names for user display - The
DO5variable (allowed scopes list) now contains["local", "user"]instead of["user", "global"] - Import optimizations for stream handling modules
This is a terminology-only change that makes the scope names more intuitive - no functionality has been altered.