Repository navigation
MCP server connection failures are logged without a reason #49726
Description
When a local MCP server fails to spawn or connect (bad binary path, server exits on startup), the runtime log only shows:
WARN server unavailable { key: "my-server", type: "local", status: "failed" }
with no reason attached. The failure message is already captured in status.error by connectLocal (opencode mcp list does print it), but the log line drops it. With several MCP servers configured, it's undiagnosable which one broke and why.
Happy to send a PR adding the reason to that log line.
Activity
neriousy commentedon Oct 20, 2026
Thanks for reporting this. The V1 logging path has been replaced in V2 (available since 2.0.0), where failed MCP connections log the server name and failure reason. Update with
opencode upgradeornpm i -g @opencode/cli@latest(desktop: update the app). Please comment or reopen if the failure reason is still missing on V2.