763 pages for accept.

Build an MCP server Model Context Protocol · in the page docs/2025-11-25/develop/build-server …h proper error handling.""" headers = {"User-Agent": USER_AGENT, "Accept": "application/geo+json"} async with httpx.AsyncClient() as client: try: response = await client.ge… Client Best Practices Model Context Protocol · in the page docs/2025-11-25/develop/clients/client-best-practices …eta-tools for searching available capabilities. A `search_tools` tool accepts a natural-language query and returns matching tool names with brief descriptions. ```typescript theme={null} // The model… Understanding Authorization in MCP Model Context Protocol · in the page docs/2025-11-25/tutorials/security/authorization …server. Rules: - Reject if 'aud' missing. - Accept if any audience entry matches the derived resource URL. - Supports string or list forms per JWT spec. """… Security Best Practices Model Context Protocol · in the page docs/2025-11-25/tutorials/security/security_best_practices …ssthrough "Token passthrough" is an anti-pattern where an MCP server accepts tokens from an MCP client without validating that the tokens were properly issued *to the MCP server* and passes them thro… Build an MCP client Model Context Protocol · in the page docs/2026-07-28/develop/build-client …tln!("\nError: {}", err), } } Ok(()) } ``` The loop accepts queries until the user types `quit` or closes standard input. Query errors are printed without terminating the client. ##… Build an MCP server Model Context Protocol · in the page docs/2026-07-28/develop/build-server …h proper error handling.""" headers = {"User-Agent": USER_AGENT, "Accept": "application/geo+json"} async with httpx2.AsyncClient() as client: try: response = await client.g… Client Best Practices Model Context Protocol · in the page docs/2026-07-28/develop/clients/client-best-practices …eta-tools for searching available capabilities. A `search_tools` tool accepts a natural-language query and returns matching tool names with brief descriptions. ```typescript theme={null} // The model… Architecture overview Model Context Protocol · in the page docs/2026-07-28/learn/architecture …and `supportedVersions` in the response lists the versions the server accepts. If a server does not support the requested version, it rejects the request with an `UnsupportedProtocolVersionError` list… Versioning Model Context Protocol · in the page docs/2026-07-28/learn/versioning …a`](/specification/2026-07-28/basic/index#meta) field, and the server accepts or rejects each request independently. On Streamable HTTP, the same value is also carried in the [`MCP-Protocol-Version` h… CLI client Model Context Protocol · in the page docs/2026-07-28/tools/inspector/cli …protocol/inspector` instead, as above. ## Choosing a server The CLI accepts a positional command (stdio), a `--server-url` (HTTP/SSE), or a named server out of a catalog or config file: ```bash the… Configuration and flags Model Context Protocol · in the page docs/2026-07-28/tools/inspector/configuration …server out of the file. | **Selects only in the CLI.** The web client accepts it but ignores it with a note, listing every server. The TUI doesn't define it (an unknown-option error) and lets you choo… mcpdo connection client Model Context Protocol · in the page docs/2026-07-28/tools/inspector/mcpdo …d, other calls on that connection are refused. URL mode is never auto-accepted. To keep a server from asking at all, connect with `--elicit off`. `--elicit url`, `form` or `both` (the default) choose… Recipes Model Context Protocol · in the page docs/2026-07-28/tools/inspector/recipes …mcp --transport http \ --header "X-Tenant: acme" ``` `--transport` accepts `http` (Streamable HTTP) and `sse`. If the server is protected, see [Authorization](/docs/2026-07-28/tools/inspector/autho… Security Model Context Protocol · in the page docs/2026-07-28/tools/inspector/security …ctor's own user, on the machine or in the container. When that is not acceptable, use a keychain or the memory store. Two failure modes are deliberately loud rather than silent: * If the key file is… Web client Model Context Protocol · in the page docs/2026-07-28/tools/inspector/web …t binding and origins By default the Inspector binds `127.0.0.1` and accepts requests only from the loopback origins for its port. Treat both defaults as security boundaries, since the backend spawns… Understanding Authorization in MCP Model Context Protocol · in the page docs/2026-07-28/tutorials/security/authorization …server. Rules: - Reject if 'aud' missing. - Accept if any audience entry matches the derived resource URL. - Supports string or list forms per JWT spec. """… Local Server Security Model Context Protocol · in the page docs/2026-07-28/tutorials/security/local-server-security …fleet: * We maintain an allowlist of approved servers with published acceptance criteria. * We continuously inventory MCP client configurations on managed machines. * We have a documented default… Security Best Practices Model Context Protocol · in the page docs/2026-07-28/tutorials/security/security_best_practices …ssthrough "Token passthrough" is an anti-pattern where an MCP server accepts tokens from an MCP client without validating that the tokens were properly issued *to the MCP server* and passes them thro… Build an MCP client Model Context Protocol · in the page docs/draft/develop/build-client …tln!("\nError: {}", err), } } Ok(()) } ``` The loop accepts queries until the user types `quit` or closes standard input. Query errors are printed without terminating the client. ##… Build an MCP server Model Context Protocol · in the page docs/draft/develop/build-server …h proper error handling.""" headers = {"User-Agent": USER_AGENT, "Accept": "application/geo+json"} async with httpx2.AsyncClient() as client: try: response = await client.g… Client Best Practices Model Context Protocol · in the page docs/draft/develop/clients/client-best-practices …eta-tools for searching available capabilities. A `search_tools` tool accepts a natural-language query and returns matching tool names with brief descriptions. ```typescript theme={null} // The model… Architecture overview Model Context Protocol · in the page docs/draft/learn/architecture …and `supportedVersions` in the response lists the versions the server accepts. If a server does not support the requested version, it rejects the request with an `UnsupportedProtocolVersionError` list… Versioning Model Context Protocol · in the page docs/draft/learn/versioning …`_meta`](/specification/draft/basic/index#meta) field, and the server accepts or rejects each request independently. On Streamable HTTP, the same value is also carried in the [`MCP-Protocol-Version` h… CLI client Model Context Protocol · in the page docs/draft/tools/inspector/cli …protocol/inspector` instead, as above. ## Choosing a server The CLI accepts a positional command (stdio), a `--server-url` (HTTP/SSE), or a named server out of a catalog or config file: ```bash the… Configuration and flags Model Context Protocol · in the page docs/draft/tools/inspector/configuration …server out of the file. | **Selects only in the CLI.** The web client accepts it but ignores it with a note, listing every server. The TUI doesn't define it (an unknown-option error) and lets you choo… mcpdo connection client Model Context Protocol · in the page docs/draft/tools/inspector/mcpdo …d, other calls on that connection are refused. URL mode is never auto-accepted. To keep a server from asking at all, connect with `--elicit off`. `--elicit url`, `form` or `both` (the default) choose… Recipes Model Context Protocol · in the page docs/draft/tools/inspector/recipes …mcp --transport http \ --header "X-Tenant: acme" ``` `--transport` accepts `http` (Streamable HTTP) and `sse`. If the server is protected, see [Authorization](/docs/draft/tools/inspector/authorizat… Security Model Context Protocol · in the page docs/draft/tools/inspector/security …ctor's own user, on the machine or in the container. When that is not acceptable, use a keychain or the memory store. Two failure modes are deliberately loud rather than silent: * If the key file is… Web client Model Context Protocol · in the page docs/draft/tools/inspector/web …t binding and origins By default the Inspector binds `127.0.0.1` and accepts requests only from the loopback origins for its port. Treat both defaults as security boundaries, since the backend spawns… Understanding Authorization in MCP Model Context Protocol · in the page docs/draft/tutorials/security/authorization …server. Rules: - Reject if 'aud' missing. - Accept if any audience entry matches the derived resource URL. - Supports string or list forms per JWT spec. """… Local Server Security Model Context Protocol · in the page docs/draft/tutorials/security/local-server-security …fleet: * We maintain an allowlist of approved servers with published acceptance criteria. * We continuously inventory MCP client configurations on managed machines. * We have a documented default… Security Best Practices Model Context Protocol · in the page docs/draft/tutorials/security/security_best_practices …ssthrough "Token passthrough" is an anti-pattern where an MCP server accepts tokens from an MCP client without validating that the tokens were properly issued *to the MCP server* and passes them thro… OAuth Client Credentials Model Context Protocol · in the page extensions/auth/oauth-client-credentials …h logic to obtain a new token before expiry. ### For MCP servers To accept client credentials tokens, your server must: **1. Validate the token** On each request, verify the JWT signature and clai… Skills Model Context Protocol · in the page extensions/skills/overview …es > `"resources": "dynamic"`. Hosts **MAY** decline these skills. If accepted, > hosts **MUST** still verify frontmatter and **MUST NOT** treat persisted > approval as covering arbitrary future conte… Tasks Model Context Protocol · in the page extensions/tasks/overview …pleted`) or `error` (on `failed`) field. **5. Handle tasks/update** Accept `inputResponses` keyed to outstanding `inputRequests`. Acknowledge with an empty result. Ignore responses for unknown or al… Official MCP Registry Terms of Service Model Context Protocol · in the page registry/terms-of-service …arrant that you have authority to bind that entity to these Terms. By accepting these Terms, you are doing so on behalf of that entity (and all references to “you” in these Terms refer to that entity)… SEP-1024: MCP Client Security Requirements for Local Server Installation Model Context Protocol · in the page seps/1024-mcp-client-security-requirements-for-local-server- …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-1034: Support default values for all primitive types in elicitation schemas Model Context Protocol · in the page seps/1034--support-default-values-for-all-primitive-types-in …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-1036: URL Mode Elicitation for secure out-of-band interactions Model Context Protocol · in the page seps/1036-url-mode-elicitation-for-secure-out-of-band-intera …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-1046: Support OAuth client credentials flow in authorization Model Context Protocol · in the page seps/1046-support-oauth-client-credentials-flow-in-authoriza …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-1302: Formalize Working Groups and Interest Groups in MCP Governance Model Context Protocol · in the page seps/1302-formalize-working-groups-and-interest-groups-in-mc …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-1303: Input Validation Errors as Tool Execution Errors Model Context Protocol · in the page seps/1303-input-validation-errors-as-tool-execution-errors …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-1319: Decouple Request Payload from RPC Methods Definition Model Context Protocol · in the page seps/1319-decouple-request-payload-from-rpc-methods-definiti …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-1330: Elicitation Enum Schema Improvements and Standards Compliance Model Context Protocol · in the page seps/1330-elicitation-enum-schema-improvements-and-standards …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-1577: Sampling With Tools Model Context Protocol · in the page seps/1577--sampling-with-tools …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-1613: Establish JSON Schema 2020-12 as Default Dialect for MCP Model Context Protocol · in the page seps/1613-establish-json-schema-2020-12-as-default-dialect-f …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-1686: Tasks Model Context Protocol · in the page seps/1686-tasks …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-1699: Support SSE polling via server-side disconnect Model Context Protocol · in the page seps/1699-support-sse-polling-via-server-side-disconnect …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-1730: SDKs Tiering System Model Context Protocol · in the page seps/1730-sdks-tiering-system …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-1850: PR-Based SEP Workflow Model Context Protocol · in the page seps/1850-pr-based-sep-workflow …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…