1,005 pages for path.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
SEP-2567: Sessionless MCP via Explicit State Handles
Model Context Protocol · in the page
seps/2567-sessionless-mcp
…hosts that regularly spawn subagents, this is a multiplier on the hot path. The possibility that a server is session-scoped forces `O(subagents × servers)` calls to `tools/list`: every subagent, for e…
SEP-2575: Make MCP Stateless
Model Context Protocol · in the page
seps/2575-stateless-mcp
…requests inside an `IncompleteResult` returned from specific request paths (e.g., `CallTool`, `GetPrompt`, `ListResources`). The client satisfies the input requests and retries the original request.…
SEP-2596: Specification Feature Lifecycle and Deprecation Policy
Model Context Protocol · in the page
seps/2596-spec-feature-lifecycle-and-deprecation
…s that "removing from \[the spec] is nearly impossible" but offers no path for the cases where removal is warranted. The Core Maintainers agreed at the [April 1, 2026 meeting][cm-2026-04-01] that MCP…
SEP-2640: Skills Extension
Model Context Protocol · in the page
seps/2640-skills-extension
…own `skill://` URI structure, with diverging semantics for authority, path, and sub-resource addressing. ## Specification ### Dependencies This extension has no dependencies beyond the base MCP Res…
SEP-2663: Tasks Extension
Model Context Protocol · in the page
seps/2663-tasks-extension
…rve the resulting state. That conflation has costs: it makes the read path non-idempotent (a retried `tasks/get` could re-submit responses), it forces the read path to share the eventual-consistency m…
SEP-932: Model Context Protocol Governance
Model Context Protocol · in the page
seps/932-model-context-protocol-governance
…ve no clear visibility into how decisions are made 2. **Participation Pathways**: Contributors lack defined ways to influence project direction 3. **Accountability**: No formal structure exists for re…
SEP-985: Align OAuth 2.0 Protected Resource Metadata with RFC 9728
Model Context Protocol · in the page
seps/985-align-oauth-20-protected-resource-metadata-with-rf
…option to discover metadata via a well-known URL provides a practical path forward for easier MCP adoption. Requiring only the header would impose significant communication overhead between components…
SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents
Model Context Protocol · in the page
seps/991-enable-url-based-client-registration-using-oauth-c
…quirements * The client\_id URL MUST use "https" scheme and contain a path component * Metadata documents MUST be valid JSON and include at minimum: * `client_id`: matching the document URL exactly…
Roots
Model Context Protocol · in the page
specification/2024-11-05/client/roots
…s with appropriate permissions * Validate all root URIs to prevent path traversal * Implement proper access controls * Monitor root accessibility 2. Servers **SHOULD**: * Handle cases whe…
Specification
Model Context Protocol · in the page
specification/2024-11-05/index
…owerful capabilities through arbitrary data access and code execution paths. With this power comes important security and trust considerations that all implementors must carefully address. ### Key Pr…
Prompts
Model Context Protocol · in the page
specification/2024-11-05/server/prompts
…ple of prompt exposed as slash command" width="293" height="106" data-path="specification/2024-11-05/server/slash-command.png" /> However, implementors are free to expose prompts through any interfac…
Resources
Model Context Protocol · in the page
specification/2024-11-05/server/resources
…lt="Example of resource context picker" width="174" height="181" data-path="specification/2024-11-05/server/resource-picker.png" /> However, implementations are free to expose resources through any i…
Completion
Model Context Protocol · in the page
specification/2024-11-05/server/utilities/completion
…eferences a resource URI | `{"type": "ref/resource", "uri": "file:///{path}"}` | ### Completion Results Servers return an array of completion values ranked by relevance, with: * Maximum 100 items p…
Authorization
Model Context Protocol · in the page
specification/2025-03-26/basic/authorization
…T** be determined from the MCP server URL by discarding any existing `path` component. For example: If the MCP server URL is `https://api.example.com/v1/mcp`, then: * The authorization base URL is `…
Transports
Model Context Protocol · in the page
specification/2025-03-26/basic/transports
…ons and requests. The server **MUST** provide a single HTTP endpoint path (hereafter referred to as the **MCP endpoint**) that supports both POST and GET methods. For example, this could be a URL lik…
Roots
Model Context Protocol · in the page
specification/2025-03-26/client/roots
…s with appropriate permissions * Validate all root URIs to prevent path traversal * Implement proper access controls * Monitor root accessibility 2. Servers **SHOULD**: * Handle cases whe…
Specification
Model Context Protocol · in the page
specification/2025-03-26/index
…owerful capabilities through arbitrary data access and code execution paths. With this power comes important security and trust considerations that all implementors must carefully address. ### Key Pr…
Prompts
Model Context Protocol · in the page
specification/2025-03-26/server/prompts
…ple of prompt exposed as slash command" width="293" height="106" data-path="specification/2025-03-26/server/slash-command.png" /> However, implementors are free to expose prompts through any interfac…
Resources
Model Context Protocol · in the page
specification/2025-03-26/server/resources
…lt="Example of resource context picker" width="174" height="181" data-path="specification/2025-03-26/server/resource-picker.png" /> However, implementations are free to expose resources through any i…
Completion
Model Context Protocol · in the page
specification/2025-03-26/server/utilities/completion
…eferences a resource URI | `{"type": "ref/resource", "uri": "file:///{path}"}` | ### Completion Results Servers return an array of completion values ranked by relevance, with: * Maximum 100 items p…
Authorization
Model Context Protocol · in the page
specification/2025-06-18/basic/authorization
…://mcp.example.com:8443` * `https://mcp.example.com/server/mcp` (when path component is necessary to identify individual MCP server) Examples of invalid canonical URIs: * `mcp.example.com` (missing…
Transports
Model Context Protocol · in the page
specification/2025-06-18/basic/transports
…ons and requests. The server **MUST** provide a single HTTP endpoint path (hereafter referred to as the **MCP endpoint**) that supports both POST and GET methods. For example, this could be a URL lik…
Roots
Model Context Protocol · in the page
specification/2025-06-18/client/roots
…s with appropriate permissions * Validate all root URIs to prevent path traversal * Implement proper access controls * Monitor root accessibility 2. Servers **SHOULD**: * Handle cases whe…
Specification
Model Context Protocol · in the page
specification/2025-06-18/index
…owerful capabilities through arbitrary data access and code execution paths. With this power comes important security and trust considerations that all implementors must carefully address. ### Key Pr…
Prompts
Model Context Protocol · in the page
specification/2025-06-18/server/prompts
…ple of prompt exposed as slash command" width="293" height="106" data-path="specification/2025-06-18/server/slash-command.png" /> However, implementors are free to expose prompts through any interfac…
Resources
Model Context Protocol · in the page
specification/2025-06-18/server/resources
…lt="Example of resource context picker" width="174" height="181" data-path="specification/2025-06-18/server/resource-picker.png" /> However, implementations are free to expose resources through any i…
Completion
Model Context Protocol · in the page
specification/2025-06-18/server/utilities/completion
…eferences a resource URI | `{"type": "ref/resource", "uri": "file:///{path}"}` | ### Completion Results Servers return an array of completion values ranked by relevance, with: * Maximum 100 items p…
Authorization
Model Context Protocol · in the page
specification/2025-11-25/basic/authorization
…tatracker.ietf.org/doc/html/rfc9728). This can be either: * At the path of the server's MCP endpoint: `https://example.com/public/mcp` could host metadata at `https://example.com/.well-known/oauth-…
Transports
Model Context Protocol · in the page
specification/2025-11-25/basic/transports
…ons and requests. The server **MUST** provide a single HTTP endpoint path (hereafter referred to as the **MCP endpoint**) that supports both POST and GET methods. For example, this could be a URL lik…
Tasks
Model Context Protocol · in the page
specification/2025-11-25/basic/utilities/tasks
…Receivers **MUST** only transition tasks through the following valid paths: 1. From `working`: may move to `input_required`, `completed`, `failed`, or `cancelled` 2. From `input_required`: may…
Roots
Model Context Protocol · in the page
specification/2025-11-25/client/roots
…s with appropriate permissions * Validate all root URIs to prevent path traversal * Implement proper access controls * Monitor root accessibility 2. Servers **SHOULD**: * Handle cases whe…
Specification
Model Context Protocol · in the page
specification/2025-11-25/index
…owerful capabilities through arbitrary data access and code execution paths. With this power comes important security and trust considerations that all implementors must carefully address. ### Key Pr…
Prompts
Model Context Protocol · in the page
specification/2025-11-25/server/prompts
…ple of prompt exposed as slash command" width="293" height="106" data-path="specification/2025-11-25/server/slash-command.png" /> However, implementors are free to expose prompts through any interfac…
Resources
Model Context Protocol · in the page
specification/2025-11-25/server/resources
…lt="Example of resource context picker" width="174" height="181" data-path="specification/2025-11-25/server/resource-picker.png" /> However, implementations are free to expose resources through any i…
Completion
Model Context Protocol · in the page
specification/2025-11-25/server/utilities/completion
…eferences a resource URI | `{"type": "ref/resource", "uri": "file:///{path}"}` | ### Completion Results Servers return an array of completion values ranked by relevance, with: * Maximum 100 items p…
Authorization Server Discovery
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/authorization-server-discovery
…tatracker.ietf.org/doc/html/rfc9728). This can be either: * At the path of the server's MCP endpoint: `https://example.com/public/mcp` could host metadata at `https://example.com/.well-known/oauth-…
Client Registration
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/client-registration
…s * The `client_id` URL **MUST** use the "https" scheme and contain a path component, e.g. `https://example.com/client.json` * The metadata document **MUST** include at least the following properties:…
Authorization
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/index
…onse_iss_parameter_supported` until that revision defines the upgrade path. After decoding the `iss` value from the `application/x-www-form-urlencoded` response per [RFC 9207 Section 2.4](https://dat…
Streamable HTTP
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/streamable-http
…ese interactions. The server **MUST** provide a single HTTP endpoint path (hereafter referred to as the **MCP endpoint**) that supports POST. For example, this could be a URL like `https://example.co…
Roots
Model Context Protocol · in the page
specification/2026-07-28/client/roots
…s with appropriate permissions * Validate all root URIs to prevent path traversal * Implement proper access controls * Monitor root accessibility 2. Servers **SHOULD**: * Handle cases whe…
Deprecated Features
Model Context Protocol · in the page
specification/2026-07-28/deprecated
…# Deprecated | Feature | Deprecation SEP | Deprecated in | Migration path | Earliest removal | | - | - | - | - | - | | [Roots](/specification/2026-07-28/client/roots) | [SEP-2577](https://github.com/…
Specification
Model Context Protocol · in the page
specification/2026-07-28/index
…owerful capabilities through arbitrary data access and code execution paths. With this power comes important security and trust considerations that all implementors must carefully address. ### Key Pr…
Prompts
Model Context Protocol · in the page
specification/2026-07-28/server/prompts
…ple of prompt exposed as slash command" width="293" height="106" data-path="specification/2026-07-28/server/slash-command.png" /> However, implementors are free to expose prompts through any interfac…
Resources
Model Context Protocol · in the page
specification/2026-07-28/server/resources
…lt="Example of resource context picker" width="174" height="181" data-path="specification/2026-07-28/server/resource-picker.png" /> However, implementations are free to expose resources through any i…
Completion
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/completion
…urce URI or URI template | `{"type": "ref/resource", "uri": "file:///{path}"}` | ### Completion Results Servers return an array of completion values ranked by relevance, with: * Maximum 100 items p…
Authorization Server Discovery
Model Context Protocol · in the page
specification/draft/basic/authorization/authorization-server-discovery
…tatracker.ietf.org/doc/html/rfc9728). This can be either: * At the path of the server's MCP endpoint: `https://example.com/public/mcp` could host metadata at `https://example.com/.well-known/oauth-…
Client Registration
Model Context Protocol · in the page
specification/draft/basic/authorization/client-registration
…s * The `client_id` URL **MUST** use the "https" scheme and contain a path component, e.g. `https://example.com/client.json` * The metadata document **MUST** include at least the following properties:…
Authorization
Model Context Protocol · in the page
specification/draft/basic/authorization/index
…onse_iss_parameter_supported` until that revision defines the upgrade path. After decoding the `iss` value from the `application/x-www-form-urlencoded` response per [RFC 9207 Section 2.4](https://dat…
Streamable HTTP
Model Context Protocol · in the page
specification/draft/basic/transports/streamable-http
…ese interactions. The server **MUST** provide a single HTTP endpoint path (hereafter referred to as the **MCP endpoint**) that supports POST. For example, this could be a URL like `https://example.co…
Roots
Model Context Protocol · in the page
specification/draft/client/roots
…s with appropriate permissions * Validate all root URIs to prevent path traversal * Implement proper access controls * Monitor root accessibility 2. Servers **SHOULD**: * Handle cases whe…