Troubleshooting
Common issues and how to fix them.
Quick Diagnosis
bash
# Check mcpx is installed
mcpx version
# Check config is valid
mcpx list
# Check a server is reachable
mcpx ping serena
# Check daemon status
mcpx daemon status
# See what would execute (without executing)
mcpx serena search_symbol --name "test" --dry-run
# Check daemon logs
cat /tmp/mcpx-serena-$(id -u).logCommon Issues
Server won't start
error: server "serena": start: exec: "uvx": executable file not found in $PATHThe server command isn't in your PATH. See Connection Errors.
Config not found
No servers configured.
Add servers to .mcpx/config.yml or ~/.mcpx/config.ymlCreate a config file or run mcpx init to import from .mcp.json. See Config Errors.
Daemon is stale
error: server "serena": daemon: connect: dial unix /tmp/mcpx-serena-501.sock: connection refusedThe daemon died but left files behind. See Daemon Issues.
Secret not found
error: server "serena": resolve env: secret get "github_token": secret not foundThe secret isn't in your keychain. See Secrets Errors.
macOS keychain popup
macOS may prompt for keychain access when mcpx reads secrets. See Platform-Specific.
By Topic
- Connection Errors — server won't start, timeout, wrong command
- Daemon Issues — stale sockets, zombies, logs
- Secrets Errors — keychain access, missing secrets
- Config Errors — YAML issues, variable resolution, merge confusion
- Platform-Specific — macOS, Linux, Windows/WSL quirks