One read of Model Context Protocolmcp-20261020T200724Z
306 pages moved out of 357 read.
Pages moved
306
significant first
Pages read
357
in this capture
Captured
20:07 UTC
Corpus hash
077a51951f96
corpus-hash
What this read moved
276-300 of 306, page 12 of 13This capture is too large to show at once. Changes 276-300 of 306 are below, significant first; the rest are on the following screens.
specification/2025-11-25/changelog Changed · +0 / -2 lines
from line 1
11# Key Changes
22
3<div id="enable-section-numbers" />
4
53This document lists changes made to the Model Context Protocol (MCP) specification since
64the previous revision, [2025-06-18](/specification/2025-06-18).
75
specification/2025-11-25/client/roots Changed · +0 / -2 lines
from line 1
11# Roots
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) provides a standardized way for clients to expose
64filesystem "roots" to servers. Roots define the boundaries of where servers can operate
75within the filesystem, allowing them to understand which directories and files they have
specification/2025-11-25/server/resources Changed · +1 / -3 lines
from line 1
11# Resources
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) provides a standardized way for servers to expose
64resources to clients. Resources allow servers to share data that provides context to
75language models, such as files, database schemas, or application-specific information.
from line 17
1917* Allow the user to search through and filter available resources
2018* Implement automatic context inclusion, based on heuristics or the AI model's selection
2119
22<img src="https://mintcdn.com/mcp/uzELntid9uQ-QMAr/specification/2025-11-25/server/resource-picker.png?fit=max&auto=format&n=uzELntid9uQ-QMAr&q=85&s=bc7bc3db17d447a69809689e5888a3ab" alt="Example of resource context picker" width="174" height="181" data-path="specification/2025-11-25/server/resource-picker.png" />
20
2321
2422However, implementations are free to expose resources through any interface pattern that
2523suits their needs—the protocol itself does not mandate any specific user
specification/2025-11-25/server/utilities/completion Changed · +0 / -2 lines
from line 1
11# Completion
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) provides a standardized way for servers to offer
64autocompletion suggestions for the arguments of prompts and resource templates. When
75users are filling in argument values for a specific prompt (identified by name) or
specification/2025-11-25/server/utilities/logging Changed · +0 / -2 lines
from line 1
11# Logging
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) provides a standardized way for servers to send
64structured log messages to clients. Clients can control logging verbosity by setting
75minimum log levels, with servers sending notifications containing severity levels,
specification/2025-11-25/server/utilities/pagination Changed · +0 / -2 lines
from line 1
11# Pagination
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) supports paginating list operations that may return
64large result sets. Pagination allows servers to yield results in smaller chunks rather
75than all at once.
specification/2026-07-28/architecture/index Changed · +0 / -2 lines
from line 1
11# Architecture
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) follows a client-host-server architecture where each
64host can run multiple client instances. MCP is a stateless protocol: every request is
75self-contained and carries its own protocol version and capabilities.
specification/2026-07-28/basic/authorization/authorization-server-discovery Changed · +0 / -2 lines
from line 1
11# Authorization Server Discovery
22
3<div id="enable-section-numbers" />
4
53This document describes the mechanisms by which MCP servers advertise their associated
64authorization servers to MCP clients, as well as the discovery process through which MCP
75clients can determine authorization server endpoints and supported capabilities.
specification/2026-07-28/basic/authorization/index Changed · +0 / -2 lines
from line 1
11# Authorization
22
3<div id="enable-section-numbers" />
4
53## Introduction
64
75### Purpose and Scope
specification/2026-07-28/basic/authorization/security-considerations Changed · +0 / -2 lines
from line 1
11# Authorization Security Considerations
22
3<div id="enable-section-numbers" />
4
53This document outlines security requirements that implementers **MUST** consider when
64building MCP clients and servers.
75
specification/2026-07-28/basic/patterns/cancellation Changed · +0 / -2 lines
from line 1
11# Cancellation
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
64through notification messages. A client **SHOULD** send a cancellation notification
75to indicate that a request it previously issued should be terminated.
specification/2026-07-28/basic/patterns/index Changed · +0 / -2 lines
from line 1
11# Overview
22
3<div id="enable-section-numbers" />
4
53This page defines the message patterns of the core protocol: the ways a
64client and server compose JSON-RPC
75[requests, responses, and notifications](/specification/2026-07-28/basic/index#messages)
specification/2026-07-28/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/2026-07-28/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/2026-07-28/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/2026-07-28/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/2026-07-28/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/2026-07-28/changelog Changed · +0 / -2 lines
from line 1
11# Key Changes
22
3<div id="enable-section-numbers" />
4
53This document lists changes made to the Model Context Protocol (MCP) specification since
64the previous revision, [2025-11-25](/specification/2025-11-25).
75
specification/2026-07-28/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)
specification/draft/architecture/index Changed · +0 / -2 lines
from line 1
11# Architecture
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) follows a client-host-server architecture where each
64host can run multiple client instances. MCP is a stateless protocol: every request is
75self-contained and carries its own protocol version and capabilities.
specification/draft/basic/authorization/authorization-server-discovery Changed · +0 / -2 lines
from line 1
11# Authorization Server Discovery
22
3<div id="enable-section-numbers" />
4
53This document describes the mechanisms by which MCP servers advertise their associated
64authorization servers to MCP clients, as well as the discovery process through which MCP
75clients can determine authorization server endpoints and supported capabilities.
specification/draft/basic/authorization/index Changed · +0 / -2 lines
from line 1
11# Authorization
22
3<div id="enable-section-numbers" />
4
53## Introduction
64
75### Purpose and Scope
specification/draft/basic/authorization/security-considerations Changed · +0 / -2 lines
from line 1
11# Authorization Security Considerations
22
3<div id="enable-section-numbers" />
4
53This document outlines security requirements that implementers **MUST** consider when
64building MCP clients and servers.
75
specification/draft/basic/patterns/cancellation Changed · +0 / -2 lines
from line 1
11# Cancellation
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
64through notification messages. A client **SHOULD** send a cancellation notification
75to indicate that a request it previously issued should be terminated.
specification/draft/basic/patterns/index Changed · +0 / -2 lines
from line 1
11# Overview
22
3<div id="enable-section-numbers" />
4
53This page defines the message patterns of the core protocol: the ways a
64client and server compose JSON-RPC
75[requests, responses, and notifications](/specification/draft/basic/index#messages)