762 pages for accept.

Tools Model Context Protocol · in the page specification/2026-07-28/server/tools …}, "inputResponses": { "github_login": { "action": "accept", "content": { "name": "octocat" } } }, "requestState": "eyJsb2NhdGlvbiI6Ik5ldyBZb3… Authorization Server Discovery Model Context Protocol · in the page specification/draft/basic/authorization/authorization-server-discovery …** assume that credentials valid for one authorization server will be accepted by another. See [Authorization Server Binding](/specification/draft/basic/authorization/client-registration#authorization… Authorization Model Context Protocol · in the page specification/draft/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/draft/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/draft/basic/index …-25 and earlier; replaced by `-32602`). Clients [**SHOULD** still accept `-32002`](/specification/draft/server/resources#error-handling) from servers implementing earlier versions. * `-32042` —… Multi Round-Trip Requests Model Context Protocol · in the page specification/draft/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/draft/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/draft/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/draft/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/draft/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… Resources Model Context Protocol · in the page specification/draft/server/resources …nternal errors. For backwards compatibility, clients **SHOULD** also accept `-32002` as a resource not found error, as earlier protocol versions used this code. Servers **MUST NOT** return an empty… Tools Model Context Protocol · in the page specification/draft/server/tools …}, "inputResponses": { "github_login": { "action": "accept", "content": { "name": "octocat" } } }, "requestState": "eyJsb2NhdGlvbiI6Ik5ldyBZb3…