Summary
tapps-mcp doctor checks for MCP config in .mcp.json, .cursor/mcp.json, and .vscode/mcp.json, but does not check .claude/settings.json mcpServers — which is a valid and common Claude Code config location.
Steps to reproduce
- Configure tapps-mcp in
.claude/settings.json under mcpServers (not .mcp.json)
- Run
tapps-mcp doctor
- Doctor reports
FAIL MCP client config: tapps-mcp not found in any MCP client config
Expected behavior
Doctor should check .claude/settings.json mcpServers as a valid config location and report PASS if tapps-mcp is configured there.
Actual behavior
Doctor only recognizes .mcp.json for Claude Code. Users who configure MCP servers in .claude/settings.json get a false failure.
Context
Discovered during initial setup of the Workstation project. The tapps-mcp entry was in .claude/settings.json and working, but doctor flagged it as missing.
Summary
tapps-mcp doctorchecks for MCP config in.mcp.json,.cursor/mcp.json, and.vscode/mcp.json, but does not check.claude/settings.jsonmcpServers— which is a valid and common Claude Code config location.Steps to reproduce
.claude/settings.jsonundermcpServers(not.mcp.json)tapps-mcp doctorFAIL MCP client config: tapps-mcp not found in any MCP client configExpected behavior
Doctor should check
.claude/settings.jsonmcpServersas a valid config location and report PASS if tapps-mcp is configured there.Actual behavior
Doctor only recognizes
.mcp.jsonfor Claude Code. Users who configure MCP servers in.claude/settings.jsonget a false failure.Context
Discovered during initial setup of the Workstation project. The tapps-mcp entry was in
.claude/settings.jsonand working, but doctor flagged it as missing.