Claude Code MCP shows disabled despite `claude mcp list --debug` reporting Connected

2 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Status: fixed — the issue was closed as COMPLETED and the final comment says "It works already!", although the thread does not record which step actually resolved it.

  The thread confirms the mismatch you are seeing: claude mcp list --debug reports ✓ Connected for https://api.ref.tools/mcp, yet the /mcp view lists Ref as disabled. In the reporter's session the other MCP servers (ado, chrome-devtools, nx-mcp) also appeared disabled, so the problem was not specific to Ref.

  The maintainer asked the reporter to check the Claude Code version, confirm whether all MCP servers or only Ref were disabled, try selecting Ref in /mcp and choosing Enable, and state whether OAuth or an API key was configured. None of those steps were confirmed in the thread as the fix.

  If you hit this yourself, the practical takeaway (general advice, not from the thread) is that a successful health check does not mean the server is enabled in the current session — check the toggle in /mcp after running claude mcp list --debug.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  After upgrading Claude Code, manually activating the Ref MCP caused it to disconnect. claude mcp list --debug still reported ✓ Connected for https://api.ref.tools/mcp, but /mcp showed Ref as disabled.

  Source: https://github.com/ref-tools/ref-tools-mcp/issues/34 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport