Skip to content
AdminKit

Server-sent events (SSE)

What is Server-sent events (SSE)?

Server-sent events (SSE) is a WHATWG web standard letting a server push a one-way stream of text events to a client over one long-lived HTTP connection. MCP's original transport paired SSE with HTTP; AdminKit's own MCP connector instead uses the Streamable HTTP transport that replaced it.

By AdminKit team, Netbase JSC · Updated

Server-sent events (SSE) is a web standard, defined in the WHATWG HTML Living Standard, that lets a server push a one-way stream of text events to a client over a single long-lived HTTP connection, without the client needing to poll repeatedly. Browsers expose it through the EventSource API, which MDN documents with examples, and a server marks such a stream with the text/event-stream content type. The Model Context Protocol used an HTTP-plus-SSE transport in its original 2024-11-05 specification for networked servers, pairing regular HTTP requests with an SSE stream for server-to-client messages, before replacing it with the Streamable HTTP transport in the 2025-03-26 specification, which folds both directions into ordinary HTTP request and response bodies instead. A progress notification reporting incremental status on a long-running call is a typical example of the server-to-client message either transport carries. A server or client built against the older transport isn’t automatically compatible with a Streamable-HTTP-only implementation, which matters when connecting an agent to an MCP server that hasn’t been updated to the current specification.

AdminKit groups server-sent events (SSE) under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does server-sent events (SSE) let a server do?

Push a one-way stream of text events to a client over a single long-lived HTTP connection, without the client needing to poll repeatedly.

Which MCP specification version used SSE as part of its transport?

The original 2024-11-05 specification's HTTP-plus-SSE transport, which paired ordinary HTTP requests with an SSE stream for server-to-client messages.

What replaced the HTTP-plus-SSE transport in MCP?

The Streamable HTTP transport, introduced in the 2025-03-26 specification, which folds both directions into ordinary HTTP request and response bodies.

Is an SSE-based MCP server automatically compatible with a Streamable-HTTP-only client?

No -- a server or client built against the older transport is not automatically compatible with an implementation that only supports Streamable HTTP.