Scope MCP Servers to User, Project, or Enterprise Level So the Right Tools Appear in the Right Context
Not every MCP server belongs everywhere. Your personal GitHub Copilot server doesn't need to show up in every project, and your team's database server shouldn't follow you to your side projects. Scoping solves this.
# User scope — available in ALL your projects (personal tools)
claude mcp add --scope user my-notes-server npx my-notes-mcp
# Project scope — shared with the team via .claude/settings.json
claude mcp add --scope project database-tools npx @company/db-mcp
# Enterprise scope — managed by your organization's admin
# (configured centrally, not via CLI)
Each scope serves a different purpose:
User scope is for personal productivity tools — servers that help you regardless of which project you're in. Things like a personal knowledge base, a calendar integration, or a documentation search tool.
Project scope is for team tools — servers that every developer on the project needs. When you add a project-scoped server, it gets saved to .claude/settings.json in your repo. Commit it, and every teammate who pulls gets the same MCP tools automatically.
# See which servers are configured at each scope
claude mcp list
# Remove a server from a specific scope
claude mcp remove --scope user old-server
A practical setup might look like:
- User: personal note-taking MCP, documentation search, calendar
- Project A (Laravel app): database query tool, Laravel docs, error monitoring
- Project B (React app): design system MCP, component library, Storybook
When you open Project A, you get the database tools. When you open Project B, you get the design system. Your personal tools are available in both. No overlap, no clutter.
Project-scoped servers are especially powerful for onboarding — a new developer clones the repo and immediately has access to every MCP tool the team uses, without manual setup.
Scope your servers like you scope your variables — as tightly as possible, as broadly as necessary.
via Claude Code
Log in to leave a comment.
MCP servers aren't just for third-party integrations — you can build your own to give Claude direct access to your internal tools, databases, APIs, and workflows. A custom MCP server turns any system your team uses into a tool Claude can call natively from your session.
Instead of manually editing settings JSON to add MCP servers, use the claude mcp command — add servers with one line, list what's configured, remove ones you don't need, and scope them to the right level, all from the terminal.
Add MCP servers to Claude Code so it can directly query your database, search documentation, check monitoring dashboards, or interact with any external service — extending what Claude can do far beyond reading files and running commands.