One read of Model Context Protocolmcp-20261020T200724Z

This capture is too large to show at once. Changes 301-306 of 306 are below, significant first; the rest are on the following screens.

specification/draft/basic/patterns/progress Changed · +0 / -2 lines

from line 1

11# Progress

22 

3<div id="enable-section-numbers" />

4 

53The Model Context Protocol (MCP) supports optional progress tracking for long-running

64operations through notification messages. The server **MAY** send progress notifications

75to report the status of requests the client has issued.

specification/draft/basic/patterns/subscriptions Changed · +0 / -2 lines

from line 1

11# Subscriptions

22 

3<div id="enable-section-numbers" />

4 

53`subscriptions/listen` opens a long-lived notification stream from the server to the

64client. Unlike one-off requests, the stream stays open and delivers notifications until

75the client cancels it. It replaces the former `resources/subscribe` RPC and the HTTP GET

specification/draft/basic/transports/index Changed · +0 / -2 lines

from line 1

11# Overview

22 

3<div id="enable-section-numbers" />

4 

53This page defines what a transport must provide to carry MCP messages, the

64standard transport bindings, and the requirements for defining new ones.

75 

specification/draft/basic/transports/stdio Changed · +0 / -2 lines

from line 1

11# stdio

22 

3<div id="enable-section-numbers" />

4 

53In the **stdio** transport, the client launches the MCP server as a subprocess.

64The two ends communicate over the subprocess's standard streams:

75 

specification/draft/basic/versioning Changed · +0 / -2 lines

from line 1

11# Versioning and Compatibility

22 

3<div id="enable-section-numbers" />

4 

53This page defines how a client and server agree on what they are speaking:

64the protocol version, declared on every request; optional extensions,

75negotiated through capabilities; and interoperability with earlier,

specification/draft/deprecated Changed · +0 / -2 lines

from line 1

11# Deprecated Features

22 

3<div id="enable-section-numbers" />

4 

53This page is the registry of specification features that are currently in the

64**Deprecated** state under the

75[feature lifecycle and deprecation policy](/community/feature-lifecycle)