How Claude Code handles MCP
Claude Code reads project and personal MCP configs, then asks you to approve servers and tools before it uses them. It is a good fit for a shared repository setup with a deliberate permission boundary.
Project or global. Project scope keeps the server with the repository; global scope makes it available in every workspace.
Teams that want MCP servers committed with the project and reviewed.
-a claude-codeWhere the MCP config lives
The installer writes this file for you. Use the paths below when you want to inspect, edit, or remove a server by hand.
.mcp.json~/.claude.jsonProject paths are relative to the workspace. Global paths are per user. On Windows, ~ means your user folder; use %USERPROFILE% in Explorer or PowerShell. A project config is shared with the team; a global config is personal.
Add a remote server
Start with a server in the MCP directory, or use your provider's endpoint. The examples use https://mcp.example.com/mcp so you can see the shape; replace it with the real URL.
- 01
Find the endpoint
Open a server page and copy its hosted endpoint. Do not use a local command or an npm package name for a remote server; those are different connection types.
Open the MCP directory - 02
Run the installer
Use the project config for a repository-specific server, or the global config for every workspace. The server name becomes
examplein the config.Claude Code · projectclaude mcp add --transport http example https://mcp.example.com/mcp --scope projectClaude Code · globalclaude mcp add --transport http example https://mcp.example.com/mcp --scope userIf the server page says SSE instead of HTTP, add
--transport sse:SSE variantclaude mcp add --transport sse example https://mcp.example.com/mcp --scope project - 03
Authorize if the provider asks
The first connection may open a browser for OAuth. Sign in with the provider and approve only the scopes you need. If the server uses an API key, create it in the provider's dashboard and add it through the client's auth flow or config.
Never paste a provider token into a project config you will commit. Prefer the client's secret store or a user-level config for credentials.
- 04
Reload and verify
Run `claude mcp list`. A project server may also need approval on first use.
Then ask for a task, not a tool: “Find the open issues assigned to me” or “Summarize the latest release.” The client decides which advertised tool to call.
What changes in the chat
Once the server is connected, its tools appear in the client's tool list. You still talk to the agent normally; MCP is plumbing, not a different chat interface.
“Find the customer notes mentioning the migration and summarize the blockers.”
“Create a draft page with this outline, but do not publish it yet.”
“Check the failed deployment and list the last three changes that touched it.”
“Which MCP tools do you have available for this task?”
If the agent ignores the server, check that the server is enabled and that its tools are approved. Some clients require a per-tool confirmation before the first call.
When it does not connect
The server is missing
Confirm the file exists at the path above, the JSON or TOML is valid, and you restarted the client or opened a new session.
It connects but tools are empty
Enable the server in the client's MCP UI, approve its tools, and check that the provider has not revoked your token.
OAuth keeps reopening
Remove the server from the client, revoke the app's access in the provider's account settings, then add it again.
A project server is ignored
Some clients require you to trust the folder before loading project MCP config. Trust the repository, then start a new session.
What to watch for in Claude Code
- A project `.mcp.json` is shared with GitHub Copilot CLI; removing a server from one removes it for the other.
- Use `--auto-approve` only for tools you have reviewed. It writes permission rules separately from the server config.
- Run `claude mcp list` to see the configured servers and their connection status.
Remove or reset the server
Remove the server when it is no longer needed, or reset it when a credential or connection state gets stuck.
- Run
claude mcp remove <name>for the scope that owns the server. - Check
.mcp.jsonor~/.claude.jsonif the command reports that no server was found. - Start a new Claude Code session and run
claude mcp list.
Remove and re-add the server to clear a stale approval or OAuth state.
Official documentation
Client behavior changes. These links are the source of truth for paths, flags, and approval behavior.