Repository navigation
Can't disable an MCP server that failed or is stuck connecting #56451
Description
In /mcps, "space" only disconnects a server that is connected. A failed server can only be retried & a pending one ignores "space".
So a server that keeps failing or hangs on connect can't be turned off from the TUI.
Also, disabling is runtime only. After a restart or config reload the server is back on.
Expected: like Claude Code, "space" toggles enabled/disabled in any state & the choice is saved to the config file that defines the server.
Activity
opencode-agent commentedon Oct 17, 2026
Thanks for the report and for opening #56452 already!
To restate the request: space in
/mcpsshould disable an MCP server whatever its state (connected, failed or still connecting), and the choice should be saved to the config file that defines the server so it survives restarts and config reloads. Right now the dialog only disconnects connected servers, offers retry for failed ones, ignores pending ones, and the toggle only changes runtime state. Maintainers will consider it.Until then, you can turn off a misbehaving server by adding
"disabled": trueto its entry in your config.Related:
opencode.json(Desktop)