188 pages for notifications.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
Elicitation
Model Context Protocol · in the page
specification/2025-11-25/client/elicitation
…he server sends a notification indicating completion. ### Completion Notifications for URL Mode Elicitation Servers **MAY** send a `notifications/elicitation/complete` notification when an out-of-ba…
Roots
Model Context Protocol · in the page
specification/2025-11-25/client/roots
…ers can request the list of roots from supporting clients and receive notifications when that list changes. ## User Interaction Model Roots in MCP are typically exposed through workspace or project…
Schema Reference
Model Context Protocol · in the page
specification/2025-11-25/schema
…mment tsd-typography"><p>A progress token, used to associate progress notifications with the original request.</p> </div> </div> <div class="type"> ### `RequestId` <div class="tsd-signature"><sp…
Prompts
Model Context Protocol · in the page
specification/2025-11-25/server/prompts
…} } } ``` `listChanged` indicates whether the server will emit notifications when the list of available prompts changes. ## Protocol Messages ### Listing Prompts To retrieve available prompt…
Resources
Model Context Protocol · in the page
specification/2025-11-25/server/resources
…individual resources. * `listChanged`: whether the server will emit notifications when the list of available resources changes. Both `subscribe` and `listChanged` are optional—servers can support…
Tools
Model Context Protocol · in the page
specification/2025-11-25/server/tools
…} } } ``` `listChanged` indicates whether the server will emit notifications when the list of available tools changes. ## Protocol Messages ### Listing Tools To discover available tools, cli…
Logging
Model Context Protocol · in the page
specification/2025-11-25/server/utilities/logging
…logging verbosity by setting minimum log levels, with servers sending notifications containing severity levels, optional logger names, and arbitrary JSON-serializable data. ## User Interaction Model…
Architecture
Model Context Protocol · in the page
specification/2026-07-28/architecture/index
…Routes protocol messages bidirectionally * Manages subscriptions and notifications * Maintains security boundaries between servers A host application creates and manages multiple clients, with each…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/index
…f the integer space is available for application-defined errors. ### Notifications [Notifications](https://modelcontextprotocol.io/specification/2026-07-28/schema.md#jsonrpcnotification) are sent fr…
Cancellation
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/cancellation
…t it previously issued should be terminated. A server **MUST** send `notifications/cancelled` referencing a `subscriptions/listen` request ID when it tears down that subscription stream (see [Subscri…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/index
…e ways a client and server compose JSON-RPC [requests, responses, and notifications](https://modelcontextprotocol.io/specification/2026-07-28/basic/index.md#messages) into interactions. Every [transpo…
Progress
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/progress
…tions through notification messages. The server **MAY** send progress notifications to report the status of requests the client has issued. ## Progress Flow When a client wants to *receive* progress…
Subscriptions
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/subscriptions
…e client. Unlike one-off requests, the stream stays open and delivers notifications until the client cancels it. It replaces the former `resources/subscribe` RPC and the HTTP GET endpoint. ## Opening…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/index
…TF-8 encoded. A binding **MUST** deliver client-sent *requests* and *notifications* to the server, and server-sent *responses* and *notifications* to the client. No other message direction exists: pe…
stdio
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/stdio
…ssages The client sends messages by writing JSON-RPC *requests* and *notifications* to the server's `stdin`, one message per line. The client **MUST NOT** write JSON-RPC *responses*. ## Receiving Me…
Streamable HTTP
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/streamable-http
…[sse] (SSE) stream scoped to that request, carrying request-related notifications followed by the final response. * Server-to-client interactions (sampling, elicitation, roots) are embedded in res…
Key Changes
Model Context Protocol · in the page
specification/2026-07-28/changelog
…rotocol/pull/2567)). 2. Make MCP stateless: remove the `initialize`/`notifications/initialized` handshake. Every request now carries its protocol version and client capabilities in `_meta` (`io.model…
Schema Reference
Model Context Protocol · in the page
specification/2026-07-28/schema
…otification with the originating subscription. The key is absent on notifications not delivered via a subscription stream (e.g. progress notifications for an in-flight request), which is why it…
Prompts
Model Context Protocol · in the page
specification/2026-07-28/server/prompts
…} } } ``` `listChanged` indicates whether the server will emit notifications when the list of available prompts changes. Servers that declare the `prompts` capability **MUST** respond to `prom…
Resources
Model Context Protocol · in the page
specification/2026-07-28/server/resources
…two optional features: * `listChanged`: whether the server will emit notifications when the list of available resources changes. * `subscribe` : whether the server supports resource-specific update…
Tools
Model Context Protocol · in the page
specification/2026-07-28/server/tools
…} } } ``` `listChanged` indicates whether the server will emit notifications when the list of available tools changes. Servers that declare the `tools` capability **MUST** respond to `tools/li…
Caching
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/caching
…d reduce unnecessary re-fetching. Caching is complementary to [change notifications](#interaction-with-notifications)—both mechanisms can coexist. ## Cacheable Results Servers MUST include caching h…
Logging
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/logging
…ntrol logging verbosity per-request via `_meta`, with servers sending notifications containing severity levels, optional logger names, and arbitrary JSON-serializable data. ## User Interaction Model…
Architecture
Model Context Protocol · in the page
specification/draft/architecture/index
…Routes protocol messages bidirectionally * Manages subscriptions and notifications * Maintains security boundaries between servers A host application creates and manages multiple clients, with each…
Overview
Model Context Protocol · in the page
specification/draft/basic/index
…f the integer space is available for application-defined errors. ### Notifications [Notifications](https://modelcontextprotocol.io/specification/draft/schema.md#jsonrpcnotification) are sent from th…
Cancellation
Model Context Protocol · in the page
specification/draft/basic/patterns/cancellation
…t it previously issued should be terminated. A server **MUST** send `notifications/cancelled` referencing a `subscriptions/listen` request ID when it tears down that subscription stream (see [Subscri…
Overview
Model Context Protocol · in the page
specification/draft/basic/patterns/index
…e ways a client and server compose JSON-RPC [requests, responses, and notifications](https://modelcontextprotocol.io/specification/draft/basic/index.md#messages) into interactions. Every [transport](h…
Progress
Model Context Protocol · in the page
specification/draft/basic/patterns/progress
…tions through notification messages. The server **MAY** send progress notifications to report the status of requests the client has issued. ## Progress Flow When a client wants to *receive* progress…
Subscriptions
Model Context Protocol · in the page
specification/draft/basic/patterns/subscriptions
…e client. Unlike one-off requests, the stream stays open and delivers notifications until the client cancels it. It replaces the former `resources/subscribe` RPC and the HTTP GET endpoint. ## Opening…
Overview
Model Context Protocol · in the page
specification/draft/basic/transports/index
…TF-8 encoded. A binding **MUST** deliver client-sent *requests* and *notifications* to the server, and server-sent *responses* and *notifications* to the client. No other message direction exists: pe…
stdio
Model Context Protocol · in the page
specification/draft/basic/transports/stdio
…ssages The client sends messages by writing JSON-RPC *requests* and *notifications* to the server's `stdin`, one message per line. The client **MUST NOT** write JSON-RPC *responses*. ## Receiving Me…
Streamable HTTP
Model Context Protocol · in the page
specification/draft/basic/transports/streamable-http
…[sse] (SSE) stream scoped to that request, carrying request-related notifications followed by the final response. * Server-to-client interactions (sampling, elicitation, roots) are embedded in res…
Schema Reference
Model Context Protocol · in the page
specification/draft/schema
…otification with the originating subscription. The key is absent on notifications not delivered via a subscription stream (e.g. progress notifications for an in-flight request), which is why it…
Prompts
Model Context Protocol · in the page
specification/draft/server/prompts
…} } } ``` `listChanged` indicates whether the server will emit notifications when the list of available prompts changes. Servers that declare the `prompts` capability **MUST** respond to `prom…
Resources
Model Context Protocol · in the page
specification/draft/server/resources
…two optional features: * `listChanged`: whether the server will emit notifications when the list of available resources changes. * `subscribe` : whether the server supports resource-specific update…
Tools
Model Context Protocol · in the page
specification/draft/server/tools
…} } } ``` `listChanged` indicates whether the server will emit notifications when the list of available tools changes. Servers that declare the `tools` capability **MUST** respond to `tools/li…
Caching
Model Context Protocol · in the page
specification/draft/server/utilities/caching
…d reduce unnecessary re-fetching. Caching is complementary to [change notifications](#interaction-with-notifications)—both mechanisms can coexist. ## Cacheable Results Servers MUST include caching h…
Logging
Model Context Protocol · in the page
specification/draft/server/utilities/logging
…ntrol logging verbosity per-request via `_meta`, with servers sending notifications containing severity levels, optional logger names, and arbitrary JSON-serializable data. ## User Interaction Model…