[DOCS] `/status` docs omit MCP server state reporting and disabled status

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

/status command description

Current Documentation

The docs currently say:

/status | Open the Settings interface (Status tab) showing version, model, account, and connectivity. Works while Claude is responding, without waiting for the current response to finish

The settings docs also describe /status only as a settings/config diagnostic surface:

Run /status inside Claude Code to see which settings sources are active and where they come from. The output shows each configuration layer (managed, user, project) along with its origin... If a settings file contains errors, /status reports the issue so you can fix it.

The MCP docs direct users to /mcp for server status:

# (within Claude Code) Check server status /mcp

What's Wrong or Missing?

Changelog v2.1.119 includes: Fixed disabled MCP servers appearing as failed in /status.

That confirms /status exposes MCP server state, and that disabled is a distinct user-visible state that should not be shown as failed.

Current Claude Code docs do not explain that /status includes MCP server diagnostics, when users should look there versus /mcp, or that intentionally disabled servers can appear in the status UI as disabled rather than failed.

This is especially relevant because the docs already describe multiple ways a server can be intentionally disabled or blocked (disabledMcpjsonServers, deniedMcpServers, and VS Code's /mcp enable/disable flow), but they do not explain how that state appears in /status.

Suggested Improvement

Update the /status documentation to mention that the Status tab also surfaces MCP server diagnostics, not just version/model/account/connectivity.

Add a short troubleshooting note or status table that explains the MCP states users may see there, including at least:

• connected
• needs-auth
• pending
• failed
• disabled

Also note that disabled can be intentional (for example, because a server was disabled in configuration or through /mcp) and should not be interpreted as a connection failure.

Cross-link that explanation to the MCP docs so /status and /mcp troubleshooting guidance stays consistent.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/commands | 84 | /status is described only as showing version, model, account, and connectivity |
| https://code.claude.com/docs/en/settings | 477 | /status is documented for active settings sources and settings-file errors |
| https://code.claude.com/docs/en/mcp | 336-337 | MCP docs currently send users to /mcp to check server status |
| https://code.claude.com/docs/en/vs-code | 351 | VS Code docs say /mcp can enable/disable servers, reconnect, and manage OAuth |
| https://code.claude.com/docs/en/settings | 180, 184, 187-188 | Settings docs define blocked/disabled/approved MCP server controls |
| https://code.claude.com/docs/en/agent-sdk/python | 1286-1297 | Agent SDK docs already enumerate MCP status values including disabled |

Total scope: 5 pages affected

Source: Changelog v2.1.119

Exact changelog entry: Fixed disabled MCP servers appearing as failed in /status