soleri-mcp-doctorlisted

# MCP Doctor — Diagnose and Heal MCP Connections Systematically diagnose why MCP servers are not connecting and attempt to repair them. ## Phase 1: Inventory Read the `.mcp.json` in the project root to get the list of configured servers. ```bash cat .mcp.json ``` For each server entry, record: - Server name - Command (`command` field) - Arguments (`args` field) - Working directory (`cwd` field, defaults to `.`) - Environment variables (`env` field, if any) ## Phase 2: Diagnose Each Server For each configured server, run these checks in order: ### 2a. Binary exists? ```bash which <command> # e.g. which node, which uvx, which npx ``` If the binary is missing, report it and suggest installation. ### 2b. Entry point exists? For `node` commands, check the script file exists: ```bash ls -la <args[0]> ``` For `npx`/`uvx` commands, check the package resolves: ```bash npx --yes <package> --help 2>&1 | head -5 # or uvx --from <source> <command> --help 2>&1 | head -5 ``` ### 2c. Server starts? Attempt to start the server with a timeout to verify it initializes: ```bash timeout 10 <full command> 2>&1 & sleep 3 kill %1 2>/dev/null ``` Look for: - Startup success messages (e.g. "Starting MCP server", "tools loaded") - Error messages (missing dependencies, port conflicts, config errors) - Crash/exit codes ### 2d. Port conflicts? If the server binds to a port, check for conflicts: ```bash lsof -i :<port> ``` If a stale process holds the port, report the PID and sugge