[BUG] Claude Clude has trouble introspecting the `claude mcp` cli

Resolved 💬 3 comments Opened Jun 12, 2025 by junoatwork Closed Dec 10, 2025

Environment

  • Platform (select one):
  • [x] AWS Bedrock
  • Claude CLI version: 1.0.17 (Claude Code)
  • Operating System: macos 15.5
  • Terminal: GhosTTY

Bug Description

Claude Code has trouble managing its own mcp servers because of server config scope. Not enough information is revealed in the claude mcp ... comand output.

Steps to Reproduce

  1. Install a --scope user MCP server in Claude Code
  2. Ask Claude to re-install it. Prompt claude to learn how via claude --help.
  • Claude should then check various subcommands like claude mcp --help, claude mcp add --help and so on
  • Claude will then likely call claude mcp list and see the server name and command listed, like foo-svc: special-server --args --etc
  • Claude will likely try running claude mcp remove foo-svc and error because it defaults to project scope, but foo-svc is a user scoped server.

Expected Behavior

  • It properly removes and re-installs
  • Claude gets enough information about itself to figure out how to successfully do that, whether through introspecting --help, an error message when the named server is in a different scope, or some other mechanism to smuggle the needed info into Claude's context.

Actual Behavior

It fails with an unhelpful error message that dead-ends, or sends Claude down a fruitless troubleshooting path.

View original on GitHub ↗

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