Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] `/status` docs omit MCP server state reporting and disabled status [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52626•Fetched 2026-04-24 06:02:06
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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:

PageLine(s)Context
https://code.claude.com/docs/en/commands84/status is described only as showing version, model, account, and connectivity
https://code.claude.com/docs/en/settings477/status is documented for active settings sources and settings-file errors
https://code.claude.com/docs/en/mcp336-337MCP docs currently send users to /mcp to check server status
https://code.claude.com/docs/en/vs-code351VS Code docs say /mcp can enable/disable servers, reconnect, and manage OAuth
https://code.claude.com/docs/en/settings180, 184, 187-188Settings docs define blocked/disabled/approved MCP server controls
https://code.claude.com/docs/en/agent-sdk/python1286-1297Agent 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

extent analysis

TL;DR

Update the /status documentation to include information about MCP server diagnostics and the different states that may be displayed.

Guidance

  • Review the current documentation for /status and identify areas where MCP server diagnostics and states are not mentioned.
  • Add a troubleshooting note or status table to the /status documentation that explains the different MCP states, including connected, needs-auth, pending, failed, and disabled.
  • Clarify that disabled can be an intentional state and should not be interpreted as a connection failure.
  • Cross-link the updated explanation to the MCP docs to ensure consistent troubleshooting guidance.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The updates should be made to the following pages: /commands, /settings, /mcp, /vs-code, and /settings. The changelog entry Fixed disabled MCP servers appearing as failed in /status confirms that /status exposes MCP server state and that disabled is a distinct user-visible state.

Recommendation

Apply workaround: Update the documentation to include the necessary information about MCP server diagnostics and states, as this will improve the understanding of the feature and reduce confusion.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#LLM response#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] `/status` docs omit MCP server state reporting and disabled status [1 participants]