claude mcp list silently omits stdio-based MCP servers from ~/.claude/mcp.json

Description

claude mcp list only shows remote HTTP-based MCP servers. stdio-based servers defined in ~/.claude/mcp.json are silently omitted from the output.

Steps to Reproduce

1. Add one or more stdio-based MCP servers to ~/.claude/mcp.json (e.g. using npx)
2. Run claude mcp list

Actual Output

Only remote HTTP servers are listed (e.g. Atlassian Rovo, Microsoft 365, Slack, Zoom):

Checking MCP server health…

claude.ai Zoom for Claude: https://mcp.zoom.us/mcp/zoom/streamable - ! Needs authentication
claude.ai Atlassian Rovo: https://mcp.atlassian.com/v1/mcp - ✓ Connected
claude.ai Microsoft 365: https://microsoft365.mcp.claude.com/mcp - ✓ Connected
claude.ai Slack: https://mcp.slack.com/mcp - ! Needs authentication

Expected Output

All configured MCP servers regardless of transport type (stdio and HTTP) should be listed.

Example ~/.claude/mcp.json (sanitized)

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "..." }
    },
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": { "MCP_JENKINS_URL": "...", "MCP_JENKINS_USER": "...", "MCP_JENKINS_API_TOKEN": "..." }
    }
  }
}

Version

Claude Code 2.1.126