Claude Code MCP Server Not Found or Not Listed: How to Fix It (Claude Code)

When Claude Code says it can't find an MCP server, or the server never shows up in /mcp or claude mcp list, the configuration usually exists but lives somewhere Claude Code isn't reading in this folder. The fastest fix is to run claude mcp list from the project folder where you want the server, check which scope it was saved in, and approve any pending .mcp.json server by running claude interactively.

Checked against: Anthropic's Claude Code MCP documentation, the Debug your configuration page and the Claude Code error reference on 2 November 2026. eSEOspace did not run these steps on your setup; follow Anthropic's pages if they differ.

What this error means

"Not found" covers a few related symptoms in Claude Code:

• The server is missing from claude mcp list or the /mcp panel.
• claude mcp get <name> or claude mcp remove <name> can't find the name.
• Claude reports Error: No such tool available: <tool name> when it tries to call one of the server's tools.
• /mcp reconnect all prints MCP server "all" not found. Anthropic's docs say that happens on versions before 2.1.284, which lack that command.

In each case, Claude Code is answering a narrow question: which servers are configured for this folder, at this moment, under this login. The scope table explains most surprises. Local and user scope live in ~/.claude.json. Project scope lives in .mcp.json at the project root.

Quick fix

1. cd into the project folder where you expect the server, then run claude mcp list.
2. If the server is not there, add it again with an explicit scope. Use --scope user if you want it in every project:

claude mcp add --transport http --scope user my-server https://example.com/mcp

1. If you use a shared .mcp.json, run claude in that folder, accept the workspace trust dialog, and approve the server when prompted.
2. Run /mcp inside the session. The server should show a status such as ✔ Connected.
3. If it shows ✘ Failed to connect instead, the server is found but can't start. Follow our failed to connect guide.

The command format above was checked against Anthropic's MCP docs on 2 November 2026. Our config generator builds the same command from a form.

Fix by client / OS

Claude Code: added in one folder, missing in another

Anthropic's docs say a local-scoped server "loads only in the project where you added it." The entry sits under that project's path in ~/.claude.json. If you ran claude mcp add from your home folder and now work in a repo, the repo has no entry. Re-add it with --scope user, or add it from the repo folder. Our guide to Claude Code MCP scopes compares the three options.

Claude Code: .mcp.json server never appears

The Debug your configuration page lists three causes:

• The file is inside .claude/ instead of the repository root.
• Servers sit under a top-level servers key, the VS Code format, instead of mcpServers.
• The one-time approval prompt was dismissed. Run /mcp to approve it.

A cloned repo can't approve its own servers. The MCP docs say enableAllProjectMcpServers committed to the project's .claude/settings.json is ignored in an untrusted folder, so the server stays pending. To reset earlier approval choices, run claude mcp reset-project-choices.

Claude Code: added to settings.json

settings.json does not read an mcpServers key, per the debug page. Move the block to .mcp.json at the project root, or use claude mcp add --scope user.

Claude Code: hidden or rejected servers

claude mcp get <name> shows statuses that claude mcp list may not:

• ✘ Rejected (see disabledMcpjsonServers in settings) means a settings entry rejects that .mcp.json server.
• ⊘ Disabled for this project (re-enable via /mcp) means it was turned off, not deleted.
• ✘ Blocked by enterprise managed policy means your organization refuses it. Anthropic notes that servers blocked by an allowlist or denylist are hidden from both commands instead, so ask your admin.

Claude Code: reserved names and failed saves

The error reference lists "workspace" is a reserved MCP server name and was not loaded. Rename the server, for example to my-workspace.

It also lists MCP server "<name>" was not saved to /home/user/.claude.json. That means the file is read-only or blocked by a sandbox. Anthropic says versions before 2.1.283 reported success even when the save failed, so an older add may never have been written.

Claude Code: claude.ai connectors are missing

Connectors you added on claude.ai load in Claude Code only when you sign in with a claude.ai subscription. The MCP docs say they are not fetched when an API key or similar method is active. Run /status to see which method is in use, then /login with your claude.ai account.

Windows, macOS and Linux paths

Anthropic's docs give one path for every OS: ~/.claude.json in your home folder for local and user scope, and .mcp.json in the project root for project scope. If you set CLAUDE_CONFIG_DIR, Claude Code reads configuration from that folder instead. Anthropic's clean-config steps copy ~/.claude.json into it, so a server saved before you set the variable can seem to vanish.

Where to find the logs

• claude mcp list and /mcp show status plus configuration warnings, such as the same name defined in more than one scope.
• claude mcp get <name> shows the scope, the command or URL, and an Issue: line for failures.
• claude --debug=mcp writes MCP details to ~/.claude/debug/<session-id>.txt, according to the debug page.
• /context shows whether any MCP tools loaded into the session at all.

If it still fails

Start Claude Code with claude --safe-mode to rule out plugins and hooks. Anthropic's docs say safe mode turns off MCP servers and other customizations for that session. If the problem is gone there, add servers back one at a time.

Also check precedence. When one name is defined in several scopes, Claude Code uses the local entry first, then project, then user, and does not merge fields. An old local entry can shadow the user entry you just fixed. Remove it with claude mcp remove <name> --scope local.

If a tool name looks wrong rather than missing, our MCP error code lookup explains common JSON-RPC errors, and the Claude Code GitHub connect guide shows a complete working setup.

Next step

If your team keeps losing track of which servers live where, a shared .mcp.json plus a short approved-server list fixes most of it. eSEOspace's Claude Code consulting team can set that up with you.

Frequently asked questions