981 pages for support.

Resources Model Context Protocol · in the page specification/2026-07-28/server/resources …e any specific user interaction model. ## Capabilities Servers that support resources **MUST** declare the `resources` capability: ```json theme={null} { "capabilities": { "resources": {… Tools Model Context Protocol · in the page specification/2026-07-28/server/tools …, to ensure a human is in the > loop ## Capabilities Servers that support tools **MUST** declare the `tools` capability: ```json theme={null} { "capabilities": { "tools": { "listChang… Caching Model Context Protocol · in the page specification/2026-07-28/server/utilities/caching # Caching The Model Context Protocol (MCP) supports caching for some results. This allows clients to cache responses and reduce unnecessary re-fetching. Caching is complementary to [change notificati… Completion Model Context Protocol · in the page specification/2026-07-28/server/utilities/completion …x#meta). ## User Interaction Model Completion in MCP is designed to support interactive user experiences similar to IDE code completion. For example, applications may show completion suggestions in… Pagination Model Context Protocol · in the page specification/2026-07-28/server/utilities/pagination # Pagination The Model Context Protocol (MCP) supports paginating list operations that may return large result sets. Pagination allows servers to yield results in smaller chunks rather than all at on… Architecture Model Context Protocol · in the page specification/draft/architecture/index …sly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the whole conversation, nor "see into" other servers** * Ser… Authorization Server Discovery Model Context Protocol · in the page specification/draft/basic/authorization/authorization-server-discovery …gh which MCP clients can determine authorization server endpoints and supported capabilities. ## Authorization Server Location MCP servers **MUST** implement the OAuth 2.0 Protected Resource Metadat… Client Registration Model Context Protocol · in the page specification/draft/basic/authorization/client-registration # Client Registration MCP supports three client registration mechanisms. Choose based on your scenario: * **[Client ID Metadata Documents](#client-id-metadata-documents)**: When client and server ha… Authorization Model Context Protocol · in the page specification/draft/basic/authorization/index …irements Authorization is **OPTIONAL** for MCP implementations. When supported: * Implementations using an HTTP-based transport **SHOULD** conform to this specification. * Implementations using an S… Authorization Security Considerations Model Context Protocol · in the page specification/draft/basic/authorization/security-considerations …ng tokens to their intended audiences **when the Authorization Server supports the capability**. To enable current and future adoption: * MCP clients **MUST** include the `resource` parameter in auth… Overview Model Context Protocol · in the page specification/draft/basic/index …earlier protocol revisions * **Message Patterns**: Messaging patterns supported by the core protocol including request and response, multi round-trip requests (MRTR), and subscribe and notify * **Auth… Cancellation Model Context Protocol · in the page specification/draft/basic/patterns/cancellation # Cancellation The Model Context Protocol (MCP) supports optional cancellation of in-progress requests through notification messages. A client **SHOULD** send a cancellation notification to indicate… Multi Round-Trip Requests Model Context Protocol · in the page specification/draft/basic/patterns/mrtr …ern. The previous pattern of server-initiated requests is no longer > supported. This is a breaking change. > [!NOTE] > > For brevity, the request examples on this page omit the `_meta` request > met… Progress Model Context Protocol · in the page specification/draft/basic/patterns/progress # Progress The Model Context Protocol (MCP) supports optional progress tracking for long-running operations through notification messages. The server **MAY** send progress notifications to report the… Subscriptions Model Context Protocol · in the page specification/draft/basic/patterns/subscriptions …et the server agreed to honor. Notification types the server does not support are omitted. ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/subscriptions/acknowledged", "params… Overview Model Context Protocol · in the page specification/draft/basic/transports/index …t-agnostic and can be implemented over any communication channel that supports bidirectional message exchange. Implementers who choose to support custom transports **MUST** preserve the JSON-RPC mess… stdio Model Context Protocol · in the page specification/draft/basic/transports/stdio …in32/procthread/job-objects ## Backward Compatibility A client that supports both modern (per-request-metadata) MCP versions and a legacy version that requires an `initialize` handshake **SHOULD** p… Streamable HTTP Model Context Protocol · in the page specification/draft/basic/transports/streamable-http …TP endpoint path (hereafter referred to as the **MCP endpoint**) that supports POST. For example, this could be a URL like `https://example.com/mcp`. [http-sse]: /specification/2024-11-05/basic/trans… Versioning and Compatibility Model Context Protocol · in the page specification/draft/basic/versioning …nt Server Client->>Server: request (with `_meta`) alt server supports requested version Server-->>Client: result else version unsupported Server-->>Client: UnsupportedProt… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …ing servers to gather necessary information dynamically. Elicitation supports two modes: * **Form mode**: Servers can request structured data from users with optional JSON schemas to validate respon… Roots Model Context Protocol · in the page specification/draft/client/roots …servers stay within roots. Servers can request the list of roots from supporting clients. ## User Interaction Model Roots in MCP are typically exposed through workspace or project configuration inte… Sampling Model Context Protocol · in the page specification/draft/client/sampling …all within a single sampling request flow. Clients **MUST** declare support for tool use via the `sampling.tools` capability to receive tool-enabled sampling requests. Servers **MUST NOT** send tool… Specification Model Context Protocol · in the page specification/draft/index …t.github.io/language-server-protocol/), which standardizes how to add support for programming languages across a whole ecosystem of development tools. In a similar way, MCP standardizes how to integra… Schema Reference Model Context Protocol · in the page specification/draft/schema …MUST return a <code>400 Bad Request</code>. If the server does not support the requested version, it MUST return an <a href="#unsupportedprotocolversionerror" class="tsd-kind-interface">Unsupported… Discovery Model Context Protocol · in the page specification/draft/server/discover # Discovery `server/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… Prompts Model Context Protocol · in the page specification/draft/server/prompts …e any specific user interaction model. ## Capabilities Servers that support prompts **MUST** declare the `prompts` capability in their [`DiscoverResult`](/specification/draft/schema#discoverresult):… Resources Model Context Protocol · in the page specification/draft/server/resources …e any specific user interaction model. ## Capabilities Servers that support resources **MUST** declare the `resources` capability: ```json theme={null} { "capabilities": { "resources": {… Tools Model Context Protocol · in the page specification/draft/server/tools …, to ensure a human is in the > loop ## Capabilities Servers that support tools **MUST** declare the `tools` capability: ```json theme={null} { "capabilities": { "tools": { "listChang… Caching Model Context Protocol · in the page specification/draft/server/utilities/caching # Caching The Model Context Protocol (MCP) supports caching for some results. This allows clients to cache responses and reduce unnecessary re-fetching. Caching is complementary to [change notificati… Completion Model Context Protocol · in the page specification/draft/server/utilities/completion …x#meta). ## User Interaction Model Completion in MCP is designed to support interactive user experiences similar to IDE code completion. For example, applications may show completion suggestions in… Pagination Model Context Protocol · in the page specification/draft/server/utilities/pagination # Pagination The Model Context Protocol (MCP) supports paginating list operations that may return large result sets. Pagination allows servers to yield results in smaller chunks rather than all at on…