Repository navigation
mcp: tool calls abort and restart the server with a large (229-tool) MCP server #59037
Description
Description
Calling any tool from the REA MCP server (229 tools) aborts the invocation and restarts the server. A trivial call (get_navigation_context({})) fails the same way as a large one (binary_session({})), so this is not response size.
The server log shows the connection succeed, then the run ends with no error and no shutdown line, and ~10-20s later a new run starts with a new run= id. Four distinct runs in 8 minutes, each right after a tool call:
18:01:19 run=33d344a6 "mcp connected" server=rea tools=229
<run ends, no error logged>
18:03:19 run=db6f1e2c "cli starting" version=2.0.30
18:03:50 run=db6f1e2c "mcp connected" server=rea tools=229
<run ends, no error logged>
18:05:39 run=83f2185f "cli starting" version=2.0.30
Reproduced 3/3 attempts. The MCP server itself is healthy: rea doctor reports "healthy": true and a direct stdio handshake against the same command returns 229 tools. Registration is reported aligned. No Request timed out precedes any abort, and there is no error in the log - the process simply disappears.
Note: the registration carries an environment.PATH override because this Windows session's inherited PATH predates the Node.js install; without it the server cannot launch at all. It is not the cause here - the connection succeeds.
Plugins
none
OpenCode version
2.0.30 (desktop, channel=latest)
Steps to reproduce
- Register a local MCP server that advertises ~229 tools (REA:
[email protected],npx -y [email protected] mcp). - Confirm
reawith 229 tools appears in the session catalog. - Call any one of its tools, e.g.
get_navigation_context({}). - The call aborts with "Tool execution interrupted" and the server restarts with a new run id.
Screenshot
No response
Operating System
Windows 10 10.0.19045.6466 x64
Terminal
OpenCode desktop app (no external terminal)
Activity
opencode-agent commentedon Oct 25, 2026
Thanks for the detailed report and the run IDs.
I couldn't trigger this on Linux. With OpenCode 2.0.30 and the same server (
[email protected]as a local MCP server,rea (229 tools)in the catalog), callingget_navigation_context({})through Code Mode worked normally. It returned REA's own "No app is open" result. Withcodemode: false, a directbinary_session({})call also worked. The OpenCode service stayed up, and nothing was interrupted. So the MCP call path doesn't seem to break with a server this size in general.In your log, the process that restarts is OpenCode's own background service (
cli startingwith a newrun=id), not the REA server. That looks like the Windows desktop app restarting its background service, which is what these issues describe (ordered by likelihood):This needs a maintainer with Windows and the desktop app to reproduce. Two things would help:
Background service is unresponsiveorEvent stream stalled.opencodefrom a terminal on that machine, outside the desktop app.