Source: MCP Specification 2026-07-28 and Changelog
The current Model Context Protocol revision: a stateless redesign that removes the initialize handshake and sessions, adds server/discover, MRTR and subscriptions/listen, and deprecates Roots, Sampling and Logging.
Contents
- What: the official MCP specification overview page and the “Key Changes” changelog for revision 2026-07-28
- Author/publisher: Model Context Protocol project (modelcontextprotocol.io)
- Date: revision 2026-07-28 (previous revision 2025-11-25); read 2026-11-14
- Original: Specification · Changelog
Summary
The overview defines MCP as JSON-RPC 2.0 messages between hosts (LLM apps), clients (connectors inside the host) and servers (capability providers), modelled on the Language Server Protocol. Servers offer resources, prompts and tools; clients may offer elicitation. Optional extensions (Tasks, Skills over MCP, MCP Apps) are negotiated explicitly. The changelog for 2026-07-28 describes the largest redesign so far: the protocol becomes stateless, every request carries its own version and capabilities, and server-initiated requests are replaced by a retry-based pattern.
Key claims
- Base protocol: JSON-RPC message format, stateless self-contained requests, per-request capability negotiation.
- Security principles: explicit user consent for data access and tool invocation; tool descriptions and annotations are untrusted unless from a trusted server; MCP itself cannot enforce these, implementors must.
- Sessions and the
Mcp-Session-Idheader are removed; servers needing cross-call state mint explicit handles passed as tool arguments (SEP-2567). - The
initialize/notifications/initializedhandshake is removed. Each request carriesio.modelcontextprotocol/protocolVersionandio.modelcontextprotocol/clientCapabilitiesin_meta(clients SHOULD also sendclientInfo); mismatches returnUnsupportedProtocolVersionError; servers MUST implementserver/discoverto advertise versions and capabilities (SEP-2575). - All results carry a required
resultType(completeorinput_required); clients treat results from older servers that omit it ascomplete. subscriptions/listenreplaces the HTTP GET stream andresources/subscribe; clients opt in to specific change notifications.pingandlogging/setLevelare removed; log level is set per request in_meta.- Tasks move out of core into an official extension (
io.modelcontextprotocol/tasks) with polling viatasks/getand input viatasks/update(SEP-2663). - Multi Round-Trip Requests (MRTR): instead of server-initiated
sampling/createMessage,elicitation/createorroots/list, a server returnsresultType: "input_required"withinputRequests; the client retries the original request withinputResponses(SEP-2322). - SSE resumability (
Last-Event-ID) is removed; a broken stream loses the request and the client re-issues it. - Minor:
tools/listSHOULD be deterministic in order (helps prompt-cache hits); list results carryttlMsandcacheScope; Streamable HTTP POSTs needMcp-Method/Mcp-Nameheaders; OpenTelemetry trace context in_meta; any JSON Schema 2020-12 keyword allowed ininputSchema/outputSchema. - Auth changes: clients MUST validate a present
issagainst the recorded issuer (RFC 9207); credentials are bound to the issuing authorization server; Dynamic Client Registration is deprecated in favour of Client ID Metadata Documents. - Deprecated (12-month minimum window): Roots, Sampling, Logging, the old HTTP+SSE transport.