[BUG] Disabled MCPs show as failed in /status

Resolved 💬 3 comments Opened Apr 21, 2026 by htonheim Closed Apr 22, 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?

/status reports disabled MCP servers (both claude.ai connectors and built-in ones like computer-use) as "failed." Disabled should be a distinct state from failed — a user who intentionally turned something off, or hasn't opted into an off-by-default feature, shouldn't see a red error indicator for it.

What Should Happen?

Disabled MCP servers should either not show up in /status or show as "x disabled" instead of a red "x failed".

Error Messages/Logs

/status:  
  Version:          2.1.116
  Session name:     /rename to add a name
  Session ID:       xYz
  cwd:              /Users/htonheim/coding
  Login method:     Claude Max account
  Organization:     xYz@xYz.com
  Email:            xYz@xYz.com

  Model:            Default Opus 4.7 with 1M context · Most capable for complex work
  MCP servers:      1 failed · /mcp
  Setting sources:  User settings, Project local settings

/mcp:
  Manage MCP servers
  1 server

    Built-in MCPs (always available)
  ❯ computer-use · ◯ disabled

  https://code.claude.com/docs/en/mcp for help

Steps to Reproduce

  1. In Claude Code, execute /mcp.
  2. Make sure at lease one MCP is disabled, for example the built in "computer-use" MCP.
  3. ESC out of "Manage MCP servers".
  4. Execute /status
  5. Observe how the disabled MCPs are listed as "failed" in red text.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.116 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

View original on GitHub ↗

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