Upstream contribution · mark3labs/mcp-go

mcp-go · Resetting event type at MCP Go stream boundaries

Rudy Celekli’s engineering portfolio · AI-assisted summary

Problem

A Server-Sent Events block with a type field and no data could leave the type set for the next block. The legacy transport could then discard an ordinary JSON-RPC response under the wrong event name.

Engineering response

Both stream readers clear the event type at every blank-line boundary, including blocks without data, so a later data-only block receives the default message type.

Evidence and scope

The merged record shows a failing regression in each reader before the correction and reports both passing afterward.

• Merged pull request #1104
• Merged source revision