StudioMCP.exe drops JSON-RPC connection (EOF) during capability discovery before initialize sequence

When an external MCP client attempts to connect to StudioMCP.exe, sending pre-flight discovery requests (such as server/discover or unhandled method probes prior to completing the traditional initialize handshake) causes StudioMCP.exe to panic and drop the IPC connection with an EOF error instead of returning a proper JSON-RPC error response.

Expected behavior

It should handshake with server/discover

1 Like

Getting this exact same bug on Windows using Antigravity. The server instantly crashes with an EOF error during the server/discover handshake.

2 Likes

the only fix we can do right now is to use a node.js file, bridge between JSON-RPC and legacy stateful MCP

1 Like

its been almost a week have they fixed it yet?