1,025 pages for path.

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… Resources Model Context Protocol · in the page specification/2025-11-25/server/resources …{ "resourceTemplates": [ { "uriTemplate": "file:///{path}", "name": "Project Files", "title": "📁 Project Files", "description": "Access files in the project d… 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.md) | [SEP-2577](https://github.c… 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… Resources Model Context Protocol · in the page specification/2026-07-28/server/resources …, "resourceTemplates": [ { "uriTemplate": "file:///{path}", "name": "Project Files", "title": "📁 Project Files", "description": "Access files in the project d… 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… Deprecated Features Model Context Protocol · in the page specification/draft/deprecated …# Deprecated | Feature | Deprecation SEP | Deprecated in | Migration path | Earliest removal | | - | - | - | - | - | | [Roots](/specification/draft/client/roots.md) | [SEP-2577](https://github.com/mo… Specification Model Context Protocol · in the page specification/draft/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… Resources Model Context Protocol · in the page specification/draft/server/resources …, "resourceTemplates": [ { "uriTemplate": "file:///{path}", "name": "Project Files", "title": "📁 Project Files", "description": "Access files in the project d… Completion Model Context Protocol · in the page specification/draft/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…