763 pages for accept.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
SEP-1865: MCP Apps - Interactive User Interfaces for MCP
Model Context Protocol · in the page
seps/1865-mcp-apps-interactive-user-interfaces-for-mcp
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2085: Governance Succession and Amendment Procedures
Model Context Protocol · in the page
seps/2085-governance-succession-and-amendment
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12
Model Context Protocol · in the page
seps/2106-json-schema-2020-12
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2127: MCP Server Cards - HTTP Server Discovery
Model Context Protocol · in the page
seps/2127-mcp-server-cards
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2133: Extensions
Model Context Protocol · in the page
seps/2133-extensions
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2148: MCP Contributor Ladder
Model Context Protocol · in the page
seps/2148-contributor-ladder
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2149: MCP Group Governance and Charter Template
Model Context Protocol · in the page
seps/2149-working-group-charter-template
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2164: Standardize Resource Not Found Error Code
Model Context Protocol · in the page
seps/2164-resource-not-found-error
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2207: OIDC-Flavored Refresh Token Guidance
Model Context Protocol · in the page
seps/2207-oidc-refresh-token-guidance
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2243: HTTP Header Standardization for Streamable HTTP Transport
Model Context Protocol · in the page
seps/2243-http-standardization
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
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
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2322: Multi Round-Trip Requests
Model Context Protocol · in the page
seps/2322-MRTR
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2468: Recommend Issuer (iss) Parameter in MCP Auth Responses
Model Context Protocol · in the page
seps/2468-recommend-issuer-claim-for-auth
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2484: Require Conformance Tests for Standards Track SEPs to Reach Final Status
Model Context Protocol · in the page
seps/2484-conformance-tests-required-for-final-seps
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2549: TTL for List Results
Model Context Protocol · in the page
seps/2549-TTL-for-list-results
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2567: Sessionless MCP via Explicit State Handles
Model Context Protocol · in the page
seps/2567-sessionless-mcp
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2575: Make MCP Stateless
Model Context Protocol · in the page
seps/2575-stateless-mcp
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2577: Deprecate Roots, Sampling, and Logging
Model Context Protocol · in the page
seps/2577-deprecate-roots-sampling-and-logging
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2596: Specification Feature Lifecycle and Deprecation Policy
Model Context Protocol · in the page
seps/2596-spec-feature-lifecycle-and-deprecation
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2640: Skills Extension
Model Context Protocol · in the page
seps/2640-skills-extension
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-2663: Tasks Extension
Model Context Protocol · in the page
seps/2663-tasks-extension
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-414: Document OpenTelemetry Trace Context Propagation Conventions
Model Context Protocol · in the page
seps/414-request-meta
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-932: Model Context Protocol Governance
Model Context Protocol · in the page
seps/932-model-context-protocol-governance
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
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
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
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
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-986: Specify Format for Tool Names
Model Context Protocol · in the page
seps/986-specify-format-for-tool-names
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-990: Enable enterprise IdP policy controls during MCP OAuth flows
Model Context Protocol · in the page
seps/990-enable-enterprise-idp-policy-controls-during-mcp-o
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
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
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
SEP-994: Shared Communication Practices/Guidelines
Model Context Protocol · in the page
seps/994-shared-communication-practicesguidelines
…nal status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to the [current > specification](/specif…
Specification Enhancement Proposals (SEPs)
Model Context Protocol · in the page
seps/index
…Review | SEP proposal ready for formal review by Core Maintainers | | Accepted | SEP accepted, awaiting reference implementation | | Final | SEP finalized with reference implementation complete | | Re…
Transports
Model Context Protocol · in the page
specification/2025-03-26/basic/transports
…-RPC messages to the MCP endpoint. 2. The client **MUST** include an `Accept` header, listing both `application/json` and `text/event-stream` as supported content types. 3. The body of the POST req…
Authorization
Model Context Protocol · in the page
specification/2025-06-18/basic/authorization
….org/archive/id/draft-ietf-oauth-v2-1-13.html#name-roles), capable of accepting and responding to protected resource requests using access tokens. An *MCP client* acts as an [OAuth 2.1 client](https:…
Transports
Model Context Protocol · in the page
specification/2025-06-18/basic/transports
…-RPC messages to the MCP endpoint. 2. The client **MUST** include an `Accept` header, listing both `application/json` and `text/event-stream` as supported content types. 3. The body of the POST req…
Elicitation
Model Context Protocol · in the page
specification/2025-06-18/client/elicitation
…={null} { "jsonrpc": "2.0", "id": 1, "result": { "action": "accept", "content": { "name": "octocat" } } } ``` #### Structured Data Request **Request:** ```json theme={null…
Schema Reference
Model Context Protocol · in the page
specification/2025-06-18/schema
…ass="tsd-signature-symbol">:</span> <span class="tsd-signature-type">"accept"</span> <span class="tsd-signature-symbol">|</span> <span class="tsd-signature-type">"decline"</span> <span class="tsd-sign…
Authorization
Model Context Protocol · in the page
specification/2025-11-25/basic/authorization
….org/archive/id/draft-ietf-oauth-v2-1-13.html#name-roles), capable of accepting and responding to protected resource requests using access tokens. An *MCP client* acts as an [OAuth 2.1 client](https:…
Transports
Model Context Protocol · in the page
specification/2025-11-25/basic/transports
…-RPC messages to the MCP endpoint. 2. The client **MUST** include an `Accept` header, listing both `application/json` and `text/event-stream` as supported content types. 3. The body of the POST req…
Tasks
Model Context Protocol · in the page
specification/2025-11-25/basic/utilities/tasks
…operation result directly. * **Task-augmented requests**: The server accepts the request and immediately returns a `CreateTaskResult` containing task data. The actual operation result becomes availab…
Elicitation
Model Context Protocol · in the page
specification/2025-11-25/client/elicitation
…={null} { "jsonrpc": "2.0", "id": 1, "result": { "action": "accept", "content": { "name": "octocat" } } } ``` #### Example: Structured Data Request **Request:** ```json th…
Schema Reference
Model Context Protocol · in the page
specification/2025-11-25/schema
…ass="tsd-signature-symbol">:</span> <span class="tsd-signature-type">"accept"</span> <span class="tsd-signature-symbol">|</span> <span class="tsd-signature-type">"decline"</span> <span class="tsd-sign…
Tools
Model Context Protocol · in the page
specification/2025-11-25/server/tools
…ject", "additionalProperties": false }` - **Recommended**: explicitly accepts only empty objects * `{ "type": "object" }` - accepts any object (including with properties) * `outputSchema`: Optiona…
Authorization Server Discovery
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/authorization-server-discovery
…** assume that credentials valid for one authorization server will be accepted by another. See [Authorization Server Binding](/specification/2026-07-28/basic/authorization/client-registration.md#autho…
Authorization
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/index
….org/archive/id/draft-ietf-oauth-v2-1-13.html#name-roles), capable of accepting and responding to protected resource requests using access tokens. An *MCP client* acts as an [OAuth 2.1 client](https:…
Authorization Security Considerations
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/security-considerations
…thorization servers **MAY** implement domain-based trust policies for accepting Client ID Metadata Documents, as described in [Section 6.4](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-m…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/index
…-25 and earlier; replaced by `-32602`). Clients [**SHOULD** still accept `-32002`](/specification/2026-07-28/server/resources#error-handling) from servers implementing earlier versions. * `-3204…
Multi Round-Trip Requests
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/mrtr
…sresult)). ```json theme={null} { "github_login": { "action": "accept", "content": { "name": "octocat" } }, "capital_of_france": { "role": "assistant", "content": {…
Streamable HTTP
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/streamable-http
…e server exposes a single HTTP endpoint (the **MCP endpoint**) that accepts POST. * The client sends every JSON-RPC request or notification as its own HTTP POST. * The server answers each request…
Versioning and Compatibility
Model Context Protocol · in the page
specification/2026-07-28/basic/versioning
…handshake. Every request carries its protocol version, and the server accepts or rejects each request independently: ```mermaid theme={null} sequenceDiagram participant Client participant Ser…
Elicitation
Model Context Protocol · in the page
specification/2026-07-28/client/elicitation
…nses` on the retried request):** ```json theme={null} { "action": "accept", "content": { "name": "octocat" } } ``` #### Example: Structured Data Request **Input request (delivered inside…
Schema Reference
Model Context Protocol · in the page
specification/2026-07-28/schema
…ass="tsd-signature-symbol">:</span> <span class="tsd-signature-type">"accept"</span> <span class="tsd-signature-symbol">|</span> <span class="tsd-signature-type">"decline"</span> <span class="tsd-sign…