Protocols
Saved & recent

Server-sent events

Also called: SSE, EventSource, text/event-stream

Server-sent events carry a sequence of text events from a server to a client over a long-lived HTTP response. The browser’s EventSource API parses the UTF-8 event stream and normally reconnects after a disconnection. This channel carries events toward the client; client commands can use separate HTTP requests.

A build dashboard might receive queued, running and finished events without polling. An event can include an ID that EventSource sends back as Last-Event-ID when reconnecting. The server must implement any replay behavior; the ID alone does not ensure that missed events are retained or delivered exactly once.

Read first
HTTP
Related
WebSocket, HTTP, MCP transports
Further reading
WHATWG HTML — Server-sent events
client server HTTP GET queued running finished one response reconnect · Last-Event-ID replay depends on the server
One HTTP response can carry many events. Event IDs help a server resume a stream if that server retains the necessary history.

View in the full Protocols collection