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
MCP: failed to get tools from Stitch - can't resolve reference #/$defs/ScreenInstance #26260
OpenCode fails to load tools from the Stitch MCP proxy even though the proxy connects successfully and discovers 14 tools.
Steps to reproduce
Configure Stitch MCP in local/proxy mode with API key
Start OpenCode
Stitch shows as "Failed to get tools" in statusline
Log output
INFO service=mcp key=stitch type=local found
INFO service=mcp key=stitch mcp stderr: [stitch-proxy] Connecting to https://stitch.googleapis.com/mcp...
INFO service=mcp key=stitch mcp stderr: [stitch-proxy] Connected to Stitch, discovered 14 tools
INFO service=mcp key=stitch mcp stderr: [stitch-proxy] Proxy server running
ERROR service=mcp key=stitch error=can't resolve reference #/$defs/ScreenInstance from id # failed to get tools from client
Kilo CLI user here seeing the same Stitch failure pattern on Windows. Direct mcp-remote-client works against https://stitch.googleapis.com/mcp with X-Goog-Api-Key, but the client fails during tool loading. If Kilo shares parser/runtime with OpenCode, this may be the same #/$defs/ScreenInstance schema resolution issue rather than auth/config. Posting as corroboration.
Activity
sam-atlas-dev commentedon May 8, 2026
I am trying to solve it as well ;/
christos-nova commentedon May 9, 2026
Kilo CLI user here seeing the same Stitch failure pattern on Windows. Direct
mcp-remote-clientworks againsthttps://stitch.googleapis.com/mcpwithX-Goog-Api-Key, but the client fails during tool loading. If Kilo shares parser/runtime with OpenCode, this may be the same#/$defs/ScreenInstanceschema resolution issue rather than auth/config. Posting as corroboration.