Docs search: form / page 30 of 32 / Source Intelligence

SEP-2207: OIDC-Flavored Refresh Token Guidance Model Context Protocol · in the page seps/2207-oidc-refresh-token-guidance …example**: Demonstration of client capability checking * **Client conformance test**: Allowing for easy validation of SDK implementations Links to implementations will be added once the SEP is accep…

SEP-2243: HTTP Header Standardization for Streamable HTTP Transport Model Context Protocol · in the page seps/2243-http-standardization …# Abstract This SEP proposes exposing critical routing and context information in standard HTTP header locations for the Streamable HTTP transport. By mirroring key fields from the JSON-RPC payload i…

SEP-2260: Require Server requests to be associated with a Client request. Model Context Protocol · in the page seps/2260-Require-Server-requests-to-be-associated-with-Client-requests …Ensures client has context for what scope the additional requested information will be used for. This allows clients to make better informed decisions on whether to provide the requested info. 4. **A…

SEP-2322: Multi Round-Trip Requests Model Context Protocol · in the page seps/2322-MRTR …s: servers must be able to process each individual request using no information other than what is present in that individual request. Note that while the goal here is to optimize the common case of…

SEP-2468: Recommend Issuer (iss) Parameter in MCP Auth Responses Model Context Protocol · in the page seps/2468-recommend-issuer-claim-for-auth …t undesirable to depend on for a security property. RFC 9207 works uniformly across registration approaches. Discarding `iss` when the server does not advertise support (strict RFC 9207 §2.4 SHOULD)…

SEP-2549: TTL for List Results Model Context Protocol · in the page seps/2549-TTL-for-list-results …able. Embedding the TTL in the JSON response body ensures it works uniformly across all transports. ## Backward Compatibility * Existing servers that do not provide it continue to work unchanged. If…

SEP-2567: Sessionless MCP via Explicit State Handles Model Context Protocol · in the page seps/2567-sessionless-mcp …handles are not a new protocol construct — there is no schema or wire format for them. They are a tool-design pattern; the protocol change is the removal of sessions, which leaves handles as the way t…

SEP-2575: Make MCP Stateless Model Context Protocol · in the page seps/2575-stateless-mcp …on (likely to a new server instance via the load balancer), and perform the entire initialization handshake again. This process is disruptive and inefficient, adding complexity around "resuma…

SEP-2577: Deprecate Roots, Sampling, and Logging Model Context Protocol · in the page seps/2577-deprecate-roots-sampling-and-logging …tures was proposed during a recent core contributor meeting. This SEP formalizes that proposal with a concrete implementation plan. See [discussion #2536][discussion-2536]. ### Roots Roots provides…

SEP-2596: Specification Feature Lifecycle and Deprecation Policy Model Context Protocol · in the page seps/2596-spec-feature-lifecycle-and-deprecation …greed at the [April 1, 2026 meeting][cm-2026-04-01] that MCP needs "a formal versioning status and a defined deprecation cycle" with "direction agreed, mechanics TBD." This SEP proposes those mechanic…

SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …skills/get` method returns any single skill's entry by URI. The skill format itself (directory structure, YAML frontmatter, naming rules, and the [progressive disclosure](https://agentskills.io/specif…

SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …s](https://modelcontextprotocol.io/extensions/overview.md) have been [formalized](https://modelcontextprotocol.io/seps/2133-extensions.md), moving tasks to an official extension gives the feature time…

SEP-3392: Extension Lifecycle Model Context Protocol · in the page seps/3392-extension-lifecycle …one client-side and one server-side, that interoperate. * Carry a conformance scenario that meets the requirements of [SEP-2484](https://modelcontextprotocol.io/seps/2484-conformance-tests-required-f…

SEP-3398: Release Cycle Updates Model Context Protocol · in the page seps/3398-release-cycle-updates …cess during the latest Core Maintainer Day at MCPCon Europe. This SEP formalizes that proposal. Unfinished proposals move to the next release. ## Specification ### Release Cadence Overview MCP gene…

SEP-414: Document OpenTelemetry Trace Context Propagation Conventions Model Context Protocol · in the page seps/414-request-meta …-context/) and [W3C Baggage](https://www.w3.org/TR/baggage/) value formats. 2. A non-normative example showing trace context in `_meta`. 3. A note clarifying why this an exception to DNS prefixin…

SEP-932: Model Context Protocol Governance Model Context Protocol · in the page seps/932-model-context-protocol-governance …ntextprotocol/pull/931) | *** ## Abstract This SEP establishes the formal governance model for the Model Context Protocol (MCP) project. It defines the organizational structure, decision-making pro…

SEP-973: Expose additional metadata for Implementations, Resources, Tools and Prompts Model Context Protocol · in the page seps/973-expose-additional-metadata-for-implementations-res …documentation (`websiteUrl`) allows clients to direct users to more information with a single click. ## Rationale This design builds on prior work in web manifests (MDN) and consolidates community f…

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 …over Server: Authenticates user Note over Server: Detects URL-formatted client_id Server->>Metadata: GET https://app.example.com/oauth/metadata.json Metadata-->>Server: JSON Metad…

SEP-994: Shared Communication Practices/Guidelines Model Context Protocol · in the page seps/994-shared-communication-practicesguidelines …among contributors 2. **GitHub Discussions**: For structured, longer-form discussions 3. **GitHub Issues**: For actionable tasks, bug reports, and feature requests Security-sensitive issues follow a…

Specification Enhancement Proposals (SEPs) Model Context Protocol · in the page seps/index …026-04-09 | | [SEP-2484](https://modelcontextprotocol.io/seps/2484-conformance-tests-required-for-final-seps.md) | Require Conformance Tests for Standards Track SEPs to Reach Final Status | Final | Pr…

Architecture Model Context Protocol · in the page specification/2024-11-05/architecture/index …sign Principles MCP is built on several key design principles that inform its architecture and implementation: 1. **Servers should be extremely easy to build** * Host applications handle complex…

Lifecycle Model Context Protocol · in the page specification/2024-11-05/basic/lifecycle …col version supported * Client capabilities * Client implementation information ```json theme={null} { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2…

Transports Model Context Protocol · in the page specification/2024-11-05/basic/transports …custom transports **MUST** ensure they preserve the JSON-RPC message format and lifecycle requirements defined by MCP. Custom transports **SHOULD** document their specific connection establishment an…

Cancellation Model Context Protocol · in the page specification/2024-11-05/basic/utilities/cancellation …be ignored: * Unknown request IDs * Already completed requests * Malformed notifications This maintains the "fire and forget" nature of notifications while allowing for race conditions in asynchron…

Ping Model Context Protocol · in the page specification/2024-11-05/basic/utilities/ping …r server can initiate a ping by sending a `ping` request. ## Message Format A ping request is a standard JSON-RPC request with no parameters: ```json theme={null} { "jsonrpc": "2.0", "id": "123…

Roots Model Context Protocol · in the page specification/2024-11-05/client/roots …acefully * Respect root boundaries in operations * Cache root information appropriately

Specification Model Context Protocol · in the page specification/2024-11-05/index …rovides a standardized way for applications to: * Share contextual information with language models * Expose tools and capabilities to AI systems * Build composable integrations and workflows The pr…

Overview Model Context Protocol · in the page specification/2024-11-05/server/index …o the model * **Tools**: Executable functions that allow models to perform actions or retrieve information Each primitive can be summarized in the following control hierarchy: | Primitive | Contro…

Prompts Model Context Protocol · in the page specification/2024-11-05/server/prompts …JvXpn/specification/2024-11-05/server/slash-command.png?fit=max\&auto=format\&n=4ZXF1PrDkEaJvXpn\&q=85\&s=ae78d658be66d75446ffd37a36e944c9) However, implementors are free to expose prompts through an…

Resources Model Context Protocol · in the page specification/2024-11-05/server/resources …ge models, such as files, database schemas, or application-specific information. Each resource is uniquely identified by a [URI](https://datatracker.ietf.org/doc/html/rfc3986). ## User Interaction Mo…

Tools Model Context Protocol · in the page specification/2024-11-05/server/tools …ith external systems, such as querying databases, calling APIs, or performing computations. Each tool is uniquely identified by a name and includes metadata describing its schema. ## User Interaction…

Completion Model Context Protocol · in the page specification/2024-11-05/server/utilities/completion …Control access to sensitive suggestions * Prevent completion-based information disclosure

Pagination Model Context Protocol · in the page specification/2024-11-05/server/utilities/pagination …over the internet, but also useful for local integrations to avoid performance issues with large data sets. ## Pagination Model Pagination in MCP uses an opaque cursor-based approach, instead of num…

Architecture Model Context Protocol · in the page specification/2025-03-26/architecture/index …sign Principles MCP is built on several key design principles that inform its architecture and implementation: 1. **Servers should be extremely easy to build** * Host applications handle complex…

Authorization Model Context Protocol · in the page specification/2025-03-26/basic/authorization …orted: * Implementations using an HTTP-based transport **SHOULD** conform to this specification. * Implementations using an STDIO transport **SHOULD NOT** follow this specification, and instead ret…

Overview Model Context Protocol · in the page specification/2025-03-26/basic/index …ith HTTP. Implementations using an HTTP-based transport **SHOULD** conform to this specification, whereas implementations using STDIO transport **SHOULD NOT** follow this specification, and instead re…

Lifecycle Model Context Protocol · in the page specification/2025-03-26/basic/lifecycle …col version supported * Client capabilities * Client implementation information ```json theme={null} { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2…

Transports Model Context Protocol · in the page specification/2025-03-26/basic/transports …custom transports **MUST** ensure they preserve the JSON-RPC message format and lifecycle requirements defined by MCP. Custom transports **SHOULD** document their specific connection establishment an…

Cancellation Model Context Protocol · in the page specification/2025-03-26/basic/utilities/cancellation …be ignored: * Unknown request IDs * Already completed requests * Malformed notifications This maintains the "fire and forget" nature of notifications while allowing for race conditions in asynchron…

Ping Model Context Protocol · in the page specification/2025-03-26/basic/utilities/ping …r server can initiate a ping by sending a `ping` request. ## Message Format A ping request is a standard JSON-RPC request with no parameters: ```json theme={null} { "jsonrpc": "2.0", "id": "123…

Progress Model Context Protocol · in the page specification/2025-03-26/basic/utilities/progress …`message` field **SHOULD** provide relevant human readable progress information. ## Behavior Requirements 1. Progress notifications **MUST** only reference tokens that: * Were provided in an acti…

Roots Model Context Protocol · in the page specification/2025-03-26/client/roots …acefully * Respect root boundaries in operations * Cache root information appropriately

Specification Model Context Protocol · in the page specification/2025-03-26/index …rovides a standardized way for applications to: * Share contextual information with language models * Expose tools and capabilities to AI systems * Build composable integrations and workflows The pr…

Overview Model Context Protocol · in the page specification/2025-03-26/server/index …o the model * **Tools**: Executable functions that allow models to perform actions or retrieve information Each primitive can be summarized in the following control hierarchy: | Primitive | Contro…

Prompts Model Context Protocol · in the page specification/2025-03-26/server/prompts …JvXpn/specification/2025-03-26/server/slash-command.png?fit=max\&auto=format\&n=4ZXF1PrDkEaJvXpn\&q=85\&s=8390583e2400c914dd404e37e014613e) However, implementors are free to expose prompts through an…

Resources Model Context Protocol · in the page specification/2025-03-26/server/resources …ge models, such as files, database schemas, or application-specific information. Each resource is uniquely identified by a [URI](https://datatracker.ietf.org/doc/html/rfc3986). ## User Interaction Mo…

Tools Model Context Protocol · in the page specification/2025-03-26/server/tools …ith external systems, such as querying databases, calling APIs, or performing computations. Each tool is uniquely identified by a name and includes metadata describing its schema. ## User Interaction…

Completion Model Context Protocol · in the page specification/2025-03-26/server/utilities/completion …Control access to sensitive suggestions * Prevent completion-based information disclosure