Description
The /mcp slash command in-session reports "No MCP servers configured" even though a project-level .mcp.json exists and claude mcp list confirms all servers are configured and most are connected.
Steps to Reproduce
- Have a project-level
.mcp.json with MCP servers defined (e.g. 15 servers)
- Open Claude Code in that project directory
- Run
/mcp in the session
- Observe:
"No MCP servers configured. Please run /doctor if this is unexpected."
- Run
claude mcp list in the terminal
- Observe: All servers are listed and most show ✓ Connected
Expected Behavior
/mcp should display the same server list as claude mcp list, reflecting the active project-level configuration.
Actual Behavior
/mcp shows "No MCP servers configured" — a false negative that suggests nothing is set up when servers are in fact connected.
Environment
- Platform: Windows 11 (win32)
- Shell: bash
- MCP config location:
.mcp.json (project-level, in working directory)
claude mcp list confirmed 10/15 servers connected successfully
Additional Context
Running /doctor and dismissing it did not resolve the issue. The discrepancy between /mcp (in-session command) and claude mcp list (CLI command) suggests the in-session command may not be reading the project-scoped config, or there is a timing/initialization issue where the config is not yet loaded when the session starts.
Description
The
/mcpslash command in-session reports "No MCP servers configured" even though a project-level.mcp.jsonexists andclaude mcp listconfirms all servers are configured and most are connected.Steps to Reproduce
.mcp.jsonwith MCP servers defined (e.g. 15 servers)/mcpin the session"No MCP servers configured. Please run /doctor if this is unexpected."claude mcp listin the terminalExpected Behavior
/mcpshould display the same server list asclaude mcp list, reflecting the active project-level configuration.Actual Behavior
/mcpshows "No MCP servers configured" — a false negative that suggests nothing is set up when servers are in fact connected.Environment
.mcp.json(project-level, in working directory)claude mcp listconfirmed 10/15 servers connected successfullyAdditional Context
Running
/doctorand dismissing it did not resolve the issue. The discrepancy between/mcp(in-session command) andclaude mcp list(CLI command) suggests the in-session command may not be reading the project-scoped config, or there is a timing/initialization issue where the config is not yet loaded when the session starts.