397 pages for capabilities.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
Authorization
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/index
…Purpose and Scope The Model Context Protocol provides authorization capabilities at the transport level, enabling MCP clients to make requests to restricted MCP servers on behalf of resource owners.…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/index
…any additional values of supported extensions that are advertised via capabilities. * A `resultType` of any value unrecognized by the client **MUST** be considered invalid. * For backward compatibilit…
Multi Round-Trip Requests
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/mrtr
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/2026-07-28/basic/inde…
Subscriptions
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/subscriptions
…"version": "1.0.0" }, "io.modelcontextprotocol/clientCapabilities": {} }, "notifications": { "toolsListChanged": true, "resourceSubscriptions": ["file:///project/c…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/index
…e message body: every request carries its protocol version and client capabilities in [`_meta.io.modelcontextprotocol/*`](/specification/2026-07-28/basic/index#meta) fields. A binding **MAY** additio…
stdio
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/stdio
…nline in the JSON-RPC message body. The protocol version, per-request capabilities, and optional client identity live in [`_meta.io.modelcontextprotocol/*`][meta-fields]; the method name and arguments…
Streamable HTTP
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/streamable-http
…"version": "1.0.0" }, "io.modelcontextprotocol/clientCapabilities": {} } } } ``` **`resources/read` request:** ```http theme={null} POST /mcp HTTP/1.1 Content-Type: applicatio…
Versioning and Compatibility
Model Context Protocol · in the page
specification/2026-07-28/basic/versioning
…n, declared on every request; optional extensions, negotiated through capabilities; and interoperability with earlier, handshake-based protocol revisions. There is no negotiation handshake. Every req…
Key Changes
Model Context Protocol · in the page
specification/2026-07-28/changelog
…handshake. Every request now carries its protocol version and client capabilities in `_meta` (`io.modelcontextprotocol/protocolVersion`, `io.modelcontextprotocol/clientCapabilities`). Clients SHOULD…
Elicitation
Model Context Protocol · in the page
specification/2026-07-28/client/elicitation
…/host and gather user consent before navigation to the target URL ## Capabilities Clients that support elicitation **MUST** declare the `elicitation` capability in `_meta.io.modelcontextprotocol/cli…
Roots
Model Context Protocol · in the page
specification/2026-07-28/client/roots
…ocol itself does not mandate any specific user interaction model. ## Capabilities Clients that support roots **MUST** declare the `roots` capability in `_meta.io.modelcontextprotocol/clientCapabilit…
Sampling
Model Context Protocol · in the page
specification/2026-07-28/client/sampling
…ess, selection, and permissions while enabling servers to leverage AI capabilities—with no server API keys necessary. Servers can request text, audio, or image-based interactions and optionally includ…
Deprecated Features
Model Context Protocol · in the page
specification/2026-07-28/deprecated
…allServers"` ([Sampling](/specification/2026-07-28/client/sampling.md#capabilities)) | [SEP-2596](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2596) | `2025-11-25` | Omit the fiel…
Specification
Model Context Protocol · in the page
specification/2026-07-28/index
…Share contextual information with language models * Expose tools and capabilities to AI systems * Build composable integrations and workflows The protocol uses [JSON-RPC](https://www.jsonrpc.org/) 2…
Schema Reference
Model Context Protocol · in the page
specification/2026-07-28/schema
…s="hl-0"> </span><span class="hl-1">"io.modelcontextprotocol/clientCapabilities"</span><span class="hl-0">: \{}</span><br /><span class="hl-0"> },</span><br /><span class="hl-0"> </span><span cla…
Discovery
Model Context Protocol · in the page
specification/2026-07-28/server/discover
…discover` lets a client query a server's supported protocol versions, capabilities, and identity before sending any other requests. Servers **MUST** implement it. ## Request The request carries no b…
Prompts
Model Context Protocol · in the page
specification/2026-07-28/server/prompts
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/2026-07-28/basic/inde…
Resources
Model Context Protocol · in the page
specification/2026-07-28/server/resources
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/2026-07-28/basic/inde…
Tools
Model Context Protocol · in the page
specification/2026-07-28/server/tools
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/2026-07-28/basic/inde…
Caching
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/caching
…AY** provide `ttlMs` without advertising `listChanged: true` in its capabilities. In this case, the client relies entirely on TTL-based freshness. * A server **MAY** advertise `listChanged: true` **…
Completion
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/completion
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/2026-07-28/basic/inde…
Logging
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/logging
…ocol itself does not mandate any specific user interaction model. ## Capabilities Servers that emit log message notifications **MUST** declare the `logging` capability: ```json theme={null} { "ca…
Pagination
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/pagination
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/2026-07-28/basic/inde…
Architecture
Model Context Protocol · in the page
specification/draft/architecture/index
…ry request is self-contained and carries its own protocol version and capabilities. This architecture enables users to integrate AI capabilities across applications while maintaining clear security bo…
Authorization Server Discovery
Model Context Protocol · in the page
specification/draft/basic/authorization/authorization-server-discovery
…CP clients can determine authorization server endpoints and supported capabilities. ## Authorization Server Location MCP servers **MUST** implement the OAuth 2.0 Protected Resource Metadata ([RFC972…
Authorization
Model Context Protocol · in the page
specification/draft/basic/authorization/index
…Purpose and Scope The Model Context Protocol provides authorization capabilities at the transport level, enabling MCP clients to make requests to restricted MCP servers on behalf of resource owners.…
Overview
Model Context Protocol · in the page
specification/draft/basic/index
…any additional values of supported extensions that are advertised via capabilities. * A `resultType` of any value unrecognized by the client **MUST** be considered invalid. * For backward compatibilit…
Multi Round-Trip Requests
Model Context Protocol · in the page
specification/draft/basic/patterns/mrtr
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/draft/basic/index#met…
Subscriptions
Model Context Protocol · in the page
specification/draft/basic/patterns/subscriptions
…"version": "1.0.0" }, "io.modelcontextprotocol/clientCapabilities": {} }, "notifications": { "toolsListChanged": true, "resourceSubscriptions": ["file:///project/c…
Overview
Model Context Protocol · in the page
specification/draft/basic/transports/index
…e message body: every request carries its protocol version and client capabilities in [`_meta.io.modelcontextprotocol/*`](/specification/draft/basic/index#meta) fields. A binding **MAY** additionally…
stdio
Model Context Protocol · in the page
specification/draft/basic/transports/stdio
…nline in the JSON-RPC message body. The protocol version, per-request capabilities, and optional client identity live in [`_meta.io.modelcontextprotocol/*`][meta-fields]; the method name and arguments…
Streamable HTTP
Model Context Protocol · in the page
specification/draft/basic/transports/streamable-http
…"version": "1.0.0" }, "io.modelcontextprotocol/clientCapabilities": {} } } } ``` **`resources/read` request:** ```http theme={null} POST /mcp HTTP/1.1 Content-Type: applicatio…
Versioning and Compatibility
Model Context Protocol · in the page
specification/draft/basic/versioning
…n, declared on every request; optional extensions, negotiated through capabilities; and interoperability with earlier, handshake-based protocol revisions. There is no negotiation handshake. Every req…
Elicitation
Model Context Protocol · in the page
specification/draft/client/elicitation
…/host and gather user consent before navigation to the target URL ## Capabilities Clients that support elicitation **MUST** declare the `elicitation` capability in `_meta.io.modelcontextprotocol/cli…
Roots
Model Context Protocol · in the page
specification/draft/client/roots
…ocol itself does not mandate any specific user interaction model. ## Capabilities Clients that support roots **MUST** declare the `roots` capability in `_meta.io.modelcontextprotocol/clientCapabilit…
Sampling
Model Context Protocol · in the page
specification/draft/client/sampling
…ess, selection, and permissions while enabling servers to leverage AI capabilities—with no server API keys necessary. Servers can request text, audio, or image-based interactions and optionally includ…
Deprecated Features
Model Context Protocol · in the page
specification/draft/deprecated
…/ `"allServers"` ([Sampling](/specification/draft/client/sampling.md#capabilities)) | [SEP-2596](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2596) | `2025-11-25` | Omit the fiel…
Specification
Model Context Protocol · in the page
specification/draft/index
…Share contextual information with language models * Expose tools and capabilities to AI systems * Build composable integrations and workflows The protocol uses [JSON-RPC](https://www.jsonrpc.org/) 2…
Schema Reference
Model Context Protocol · in the page
specification/draft/schema
…s="hl-0"> </span><span class="hl-1">"io.modelcontextprotocol/clientCapabilities"</span><span class="hl-0">: \{}</span><br /><span class="hl-0"> },</span><br /><span class="hl-0"> </span><span cla…
Discovery
Model Context Protocol · in the page
specification/draft/server/discover
…discover` lets a client query a server's supported protocol versions, capabilities, and identity before sending any other requests. Servers **MUST** implement it. ## Request The request carries no b…
Prompts
Model Context Protocol · in the page
specification/draft/server/prompts
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/draft/basic/index#met…
Resources
Model Context Protocol · in the page
specification/draft/server/resources
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/draft/basic/index#met…
Tools
Model Context Protocol · in the page
specification/draft/server/tools
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/draft/basic/index#met…
Caching
Model Context Protocol · in the page
specification/draft/server/utilities/caching
…AY** provide `ttlMs` without advertising `listChanged: true` in its capabilities. In this case, the client relies entirely on TTL-based freshness. * A server **MAY** advertise `listChanged: true` **…
Completion
Model Context Protocol · in the page
specification/draft/server/utilities/completion
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/draft/basic/index#met…
Logging
Model Context Protocol · in the page
specification/draft/server/utilities/logging
…ocol itself does not mandate any specific user interaction model. ## Capabilities Servers that emit log message notifications **MUST** declare the `logging` capability: ```json theme={null} { "ca…
Pagination
Model Context Protocol · in the page
specification/draft/server/utilities/pagination
…odelcontextprotocol/clientInfo`, and > `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include > the required `_meta` fields; see > [`_meta`](/specification/draft/basic/index#met…