Repository navigation
mcp list reports "No MCP servers configured" on cold start (v2.2.6) #62902
Description
Description
Summary
Immediately after the CLI/server starts, opencode mcp list prints No MCP servers configured, although the MCP servers are configured and working. Running the same command a few seconds later prints the correct status. A live session (opencode run) sees the same servers, so the configuration is valid.
Environment
- OpenCode: v2.2.6
- OS: Linux (Ubuntu, kernel 5.15) and Windows 11 — reproduced on both
- Config:
~/.config/opencode/opencode.jsonwithmcp.servers.{context7, vault}on Linux andmcp.{context7, vault}on Windows; both load fine in a session - MCP:
context7(remote),vault(local stdio python server); Linux also haschrome-devtools-hermes
Actual vs expected
First call: No MCP servers configured. Second call: ✓ context7 connected, ✓ vault connected (and ✓ chrome-devtools-hermes connected on Linux).
Expected: wait for MCP startup within the command budget, or report connecting instead of claiming nothing is configured.
Workarounds
- Re-run the command after a few seconds.
opencode mcp list --print-logs(--log-level debug --print-logs) prints the statuses even on the cold-start path.
Notes
opencode debug config lists the same servers at the moment mcp list claims there are none, so the config loader is fine and only the mcp list status path is affected.
Plugins
2.2.6
OpenCode version
No response
Steps to reproduce
- Make sure no OpenCode background service is running (fresh shell, first run after boot).
- Run
opencode mcp list. - Observe
No MCP servers configured. - Wait ~5-10 s and run
opencode mcp listagain -> the servers are listed as connected.
Screenshot
No response
Operating System
Linux (Ubuntu, kernel 5.15) and Windows 11
Terminal
bash (Linux), PowerShell (Windows)
Activity
opencodejr commentedon Nov 9, 2026
Thanks for the clear report and the workarounds. I think this is a duplicate of #54192. There, too, the first
opencode mcp listin a location that hasn't loaded yet reads the MCP list before the configured servers are registered, so it printsNo MCP servers configured, and the next call lists them correctly. In v2.2.6, the server'smcp.listhandler still doesn't wait for that registration, which matches what you see.Possible duplicates and related issues, ordered from most to least likely:
mcp list(empty on the first call, correct on the next); still open, with a proposed fix in fix(server): wait for MCP handler readiness #54191mcp listshowsNo MCP servers configuredevery time, even after a restart (servers never register), so it's related but not the samemcp list; related, but it doesn't go away on a second callopencode plugin listprints "No plugins found" on the first call per cold location #54654: the same startup race, but inopencode plugin listThe bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. If it's the same, adding your 2.2.6 Linux/Windows details as a comment on #54192 would help show that it still happens.