[BUG] /mcp command shows misleading "Project MCPs" label for global MCP servers

Resolved 💬 3 comments Opened Mar 14, 2026 by jordy-dam Closed May 4, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When running the /mcp command in a directory without a .mcp.json file, the output incorrectly labels global MCP servers as "Project MCPs" and references a non-existent file path.

Current Behavior:

Project MCPs (/path/to/project/.mcp.json)
❯ context7 · ✔ connected
obsidian · ✔ connected
sequential-thinking · ✔ connected

Even though /path/to/project/.mcp.json does not exist.

What Should Happen?

Expected Behavior:

Either:

  1. Display these as "User MCPs" (since they're coming from ~/.claude/config.json)
  2. Don't reference a non-existent file path
  3. Only show the "Project MCPs" section if a .mcp.json file actually exists in the current directory

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Navigate to a directory without a .mcp.json file
  2. Run /mcp
  3. Observe the misleading "Project MCPs" label and file path

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗