Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] /mcp dialog hides servers with zero tools, blocking mid-session reconnect

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…

When a remote HTTP MCP server connects successfully but returns zero tools from tools/list (e.g. due to a network blip at session startup), the /mcp dialog does not show that server at all. This makes it impossible to manually reconnect or re-probe the server mid-session, leaving the user with no recovery path short of /clear and losing conversation context.

Root Cause

This compounds an existing startup reliability issue with remote HTTP MCPs:

  1. Network blip at startup → tools/list probe fails silently → zero tools registered (related: #55914, #42148)
  2. /mcp dialog hides the server → no reconnect path → user is stuck for the entire session

The two bugs together make the "connected but no tools" state unrecoverable without losing context. Fixing the dialog to show all registered servers (filtering by tool count for display purposes only, not for visibility) would restore the manual recovery path even while the underlying startup reliability issue is separately addressed.

Fix Action

Workaround

None available mid-session. User must start a new session and hope the network is stable at startup.

— Claude Sonnet 4.6 on behalf of @tmeneau

RAW_BUFFERClick to expand / collapse

Summary

When a remote HTTP MCP server connects successfully but returns zero tools from tools/list (e.g. due to a network blip at session startup), the /mcp dialog does not show that server at all. This makes it impossible to manually reconnect or re-probe the server mid-session, leaving the user with no recovery path short of /clear and losing conversation context.

Steps to reproduce

  1. Start a Claude Code session with one or more remote HTTP MCP servers configured (e.g. claude.ai Datadog, claude.ai Atlassian).
  2. Have a brief network interruption at session startup so that the tools/list probe fails silently — the server will still show ✓ Connected in claude mcp list because the OAuth token check succeeds, but the tool schemas were never registered.
  3. Open the /mcp dialog.

Expected behavior

The /mcp dialog shows all registered MCP servers, regardless of how many tools they returned. Servers in a "connected but zero tools" state should be visible and offer a Reconnect option to re-run tools/list.

Actual behavior

The /mcp dialog only shows servers that have at least one registered tool. Servers in the "connected + zero tools" state are completely hidden from the dialog, so there is no UI path to reconnect them.

Why this matters

This compounds an existing startup reliability issue with remote HTTP MCPs:

  1. Network blip at startup → tools/list probe fails silently → zero tools registered (related: #55914, #42148)
  2. /mcp dialog hides the server → no reconnect path → user is stuck for the entire session

The two bugs together make the "connected but no tools" state unrecoverable without losing context. Fixing the dialog to show all registered servers (filtering by tool count for display purposes only, not for visibility) would restore the manual recovery path even while the underlying startup reliability issue is separately addressed.

Environment

  • Platform: macOS
  • Claude Code CLI
  • Remote HTTP MCP servers via claude.ai integration (OAuth)

Workaround

None available mid-session. User must start a new session and hope the network is stable at startup.

— Claude Sonnet 4.6 on behalf of @tmeneau

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…

FAQ

Expected behavior

The /mcp dialog shows all registered MCP servers, regardless of how many tools they returned. Servers in a "connected but zero tools" state should be visible and offer a Reconnect option to re-run tools/list.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING