Question

When an MCP server must provide long-running, asynchronous updates to a host, which specific transport mechanism is required to maintain the connection?

Accepted Answer

When an MCP server needs to provide long-running, asynchronous updates to a host, the required transport mechanism is Stdio (Standard Input/Output) over a persistent process connection or an SSE (Server-Sent Events) transport. Stdio enables this by treating the connection as a continuous data stream between the host and the server process, where the server can push notifications or progress updates at any time. SSE is an HTTP-based standard specifically designed for this purpose, allowing a server to push data to a web client over a single, long-lived HTTP connection. In this context, an asynchronous update is a message sent by the server that does not correspond to a specific request from the host. By using either Stdio or SSE, the transport layer remains open, allowing the server to initiate communication whenever an event occurs, ensuring the host receives information immediately without having to constantly poll or check the server for new data.

Home → All Courses → Programming Courses → Model Context Protocol (MCP) Certification → Flashcard

When an MCP server must provide long-running, asynchronous updates to a host, which specific transport mechanism is required to maintain the connection?

When an MCP server needs to provide long-running, asynchronous updates to a host, the required transport mechanism is Stdio (Standard Input/Output) over a persistent process connection or an SSE (Server-Sent Events) transport. Stdio enables this by treating the connection as a continuous....