You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Failed to get tools" when MCP server returns outputSchema in tools/list response #21373
Description
opencode v1.3.17 fails to load tools from MCP servers whose tools/list response includes the outputSchema field on tool definitions. The server is marked as failed with "Failed to get tools".
outputSchema is a valid optional field in the MCP specification and is defined in the bundled SDK's ToolSchema.
Steps to Reproduce
Set up any MCP server (stdio transport) that returns outputSchema on its tools in the tools/list response
Configure it in opencode as a local MCP server
Start opencode — the server fails with "Failed to get tools"
Observed Behavior
The MCP server starts, initialize handshake completes successfully
tools/list returns a valid response with all tools
opencode immediately closes the connection after receiving the response
Server is marked as failed
Expected Behavior
Tools should load successfully. Removing outputSchema from the response (via a wrapper script) resolves the issue — all tools load and work correctly.
This was a legitimate failure in v1.3.17, though the trigger was more specifically an outputSchema with unresolved or otherwise problematic schema references rather than every outputSchema. It was tracked more precisely in #26529 and fixed by #26614, which shipped in v1.14.46. Closing as fixed/duplicate.
Activity
rekram1-node commentedon Jun 22, 2026
This was a legitimate failure in v1.3.17, though the trigger was more specifically an
outputSchemawith unresolved or otherwise problematic schema references rather than everyoutputSchema. It was tracked more precisely in #26529 and fixed by #26614, which shipped in v1.14.46. Closing as fixed/duplicate.