[BUG] Disabled MCPs show as failed in /status
Status Fixed / completed
Reported on v2.1.116
Maintainer reply None cached
Activity 3 comments · opened Apr 21, 2026 · 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
- In Claude Code, execute /mcp.
- Make sure at lease one MCP is disabled, for example the built in "computer-use" MCP.
- ESC out of "Manage MCP servers".
- Execute /status
- 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
3 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
True that duplicate issues was found, but they are closed as duplicates that if you follow the duplication chain eventually end up as "Closed not planned" because of inactivity. Basically real bug reports seem doomed from the start because the Claude Code bot rummaging around here has created a chain of duplicates ending up in an issue closed from inactivity.
In short, none of the duplicates have been resolved, just closed as either duplicates of something else or auto closed as not planned because of inactivity.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.