347 pages for approve.

Connect to local MCP servers Model Context Protocol · in the page docs/2026-07-28/develop/connect-local-servers …operation](https://mintcdn.com/mcp/4ZXF1PrDkEaJvXpn/images/quickstart-approve.png?fit=max\&auto=format\&n=4ZXF1PrDkEaJvXpn\&q=85\&s=98cc6e9dfe885fbd6e9bfae40601e494) Review each request carefully bef… Understanding MCP clients Model Context Protocol · in the page docs/2026-07-28/learn/client-concepts …t->>User: Present request for approval User-->>Client: Review and approve/modify Note over Client,LLM: Model interaction Client->>LLM: Forward approved request LLM-->>Client: Return g… mcpdo connection client Model Context Protocol · in the page docs/2026-07-28/tools/inspector/mcpdo …hell: ```bash theme={null} mcpdo elicitation/respond <elicitationId> approved:=true # form fields as key:=value or JSON mcpdo elicitation/respond <elicitationId> --done # URL mode: I fini… Local Server Security Model Context Protocol · in the page docs/2026-07-28/tutorials/security/local-server-security …at install time either: a server can quietly change them after you approved it (a rug pull), so a one-time consent dialog and package pinning do not cover this surface. 5. **A vulnerable server… Security Best Practices Model Context Protocol · in the page docs/2026-07-28/tutorials/security/security_best_practices …consent screen Note over UA: Review consent screen UA->>TAS: Approve TAS->>UA: Set consent cookie for client ID: mcp-proxy TAS->>UA: 3P Authorization code + redirect to mcp-proxy-serv… Connect to local MCP servers Model Context Protocol · in the page docs/draft/develop/connect-local-servers …operation](https://mintcdn.com/mcp/4ZXF1PrDkEaJvXpn/images/quickstart-approve.png?fit=max\&auto=format\&n=4ZXF1PrDkEaJvXpn\&q=85\&s=98cc6e9dfe885fbd6e9bfae40601e494) Review each request carefully bef… Understanding MCP clients Model Context Protocol · in the page docs/draft/learn/client-concepts …t->>User: Present request for approval User-->>Client: Review and approve/modify Note over Client,LLM: Model interaction Client->>LLM: Forward approved request LLM-->>Client: Return g… mcpdo connection client Model Context Protocol · in the page docs/draft/tools/inspector/mcpdo …hell: ```bash theme={null} mcpdo elicitation/respond <elicitationId> approved:=true # form fields as key:=value or JSON mcpdo elicitation/respond <elicitationId> --done # URL mode: I fini… Local Server Security Model Context Protocol · in the page docs/draft/tutorials/security/local-server-security …at install time either: a server can quietly change them after you approved it (a rug pull), so a one-time consent dialog and package pinning do not cover this surface. 5. **A vulnerable server… Security Best Practices Model Context Protocol · in the page docs/draft/tutorials/security/security_best_practices …consent screen Note over UA: Review consent screen UA->>TAS: Approve TAS->>UA: Set consent cookie for client ID: mcp-proxy TAS->>UA: 3P Authorization code + redirect to mcp-proxy-serv… Enterprise-Managed Authorization Model Context Protocol · in the page extensions/auth/enterprise-managed-authorization …1. **Centralized policy**: The enterprise IdP maintains a registry of approved MCP servers and the access policies for each. Administrators configure these in their existing identity management tools.… OAuth Client Credentials Model Context Protocol · in the page extensions/auth/oauth-client-credentials …The standard MCP authorization flow requires a user to interactively approve access — a browser opens, the user logs in, and grants permission. That works well for humans, but breaks down when there'… Extensions Overview Model Context Protocol · in the page extensions/overview …core specification. The stage decides which changes are allowed, who approves them, and what implementers can expect. For full details, see [SEP-3392: Extension Lifecycle](https://modelcontextprotoco… Skills Model Context Protocol · in the page extensions/skills/overview …r: Request approval for this skill and manifest User-->>Host: Approve end Host->>Server: resources/read (SKILL.md URI) Server-->>Host: SKILL.md content Host->>Host: Verify byt… How to Automate Publishing with GitHub Actions Model Context Protocol · in the page registry/github-actions …ted-branches/about-protected-branches). Now only reviewed, maintainer-approved code can ever reach the token. 3. **(Strongest) Add a [required reviewer](https://docs.github.com/en/actions/how-tos/depl… Official MCP Registry Terms of Service Model Context Protocol · in the page registry/terms-of-service …of third party rights or terms of service. 3. Log in via method(s) approved by the Registry maintainers, which may involve using applications or other software owned by third parties. 3. Entity Us… 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- …en with these controls, risks remain: * **User Override**: Users may approve malicious commands despite warnings * **Sophisticated Obfuscation**: Advanced attackers may craft commands that appear leg… 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 …Discord channel. Majority positive vote by members over a 72h period approves creation of the group. Can be reversed at any time (e.g. after more input comes in). Core and lead maintainers can veto.… SEP-1577: Sampling With Tools Model Context Protocol · in the page seps/1577--sampling-with-tools …needed to avoid High potential for privacy leaks / abuse * If user approves Gmail MCP tool usage / delegation by mistake, server gets access to their private emails through sampling ### Allow serv… SEP-2085: Governance Succession and Amendment Procedures Model Context Protocol · in the page seps/2085-governance-succession-and-amendment …only be proposed by Lead Maintainers. Any proposed amendment must be approved by a two-thirds (2/3) majority of all Core Maintainers to take effect. Amendment proposals shall: 1. Be submitted in wr… SEP-2133: Extensions Model Context Protocol · in the page seps/2133-extensions …he final authority over its inclusion as an Official Extension. Once approved, the author SHOULD produce a PR that introduces the extension to the extension repository and reference in the main spec… SEP-2148: MCP Contributor Ladder Model Context Protocol · in the page seps/2148-contributor-ladder …proval:** * Sponsored by an existing Maintainer or Core Maintainer * Approved by Core Maintainers **Responsibilities:** * Operational ownership of area health (test stability, documentation currenc… SEP-2149: MCP Group Governance and Charter Template Model Context Protocol · in the page seps/2149-working-group-charter-template …tainer (who should notify all Core Maintainers) * Initial member list approved by WG Lead **Interest Group Formation:** * Fill out the creation template in the `#wg-ig-group-creation` channel on [Di… 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 …judges.** Rejected: concentrates veto power in a group not elected to approve spec changes. The traceability-file model lets the sponsor verify completeness without reading test code. ## Backward Com… SEP-2596: Specification Feature Lifecycle and Deprecation Policy Model Context Protocol · in the page seps/2596-spec-feature-lifecycle-and-deprecation …| Sponsor | A Maintainer or Core Maintainer, per the SEP process | | Approve a deprecation SEP | Core Maintainers, per the [governance decision process][governance-decisions] | | Decide a removal dur… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …on requires fresh consent.** Approval is per skill: approving a skill approves that skill alone and says nothing about skills nested within it. Activating a nested skill (loading it as a skill in its… SEP-3392: Extension Lifecycle Model Context Protocol · in the page seps/3392-extension-lifecycle …ge changes. The stage decides which protocol changes are allowed, who approves them, and what stability implementers can expect. Experimental and Beta extensions iterate with Extension Maintainer app… 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 …>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redirect_uri Client->>Server: Exchange code for token<… Sampling Model Context Protocol · in the page specification/2024-11-05/client/sampling …t->>User: Present request for approval User-->>Client: Review and approve/modify Note over Client,LLM: Model interaction Client->>LLM: Forward approved request LLM-->>Client: Return g… Specification Model Context Protocol · in the page specification/2024-11-05/index …zing its use 4. **LLM Sampling Controls** * Users must explicitly approve any LLM sampling requests * Users should control: * Whether sampling occurs at all * The actual prompt that w… Sampling Model Context Protocol · in the page specification/2025-03-26/client/sampling …t->>User: Present request for approval User-->>Client: Review and approve/modify Note over Client,LLM: Model interaction Client->>LLM: Forward approved request LLM-->>Client: Return g… Specification Model Context Protocol · in the page specification/2025-03-26/index …zing its use 4. **LLM Sampling Controls** * Users must explicitly approve any LLM sampling requests * Users should control: * Whether sampling occurs at all * The actual prompt that w… Elicitation Model Context Protocol · in the page specification/2025-06-18/client/elicitation …nse actions are: 1. **Accept** (`action: "accept"`): User explicitly approved and submitted with data * The `content` field contains the submitted data matching the requested schema * Example:… Sampling Model Context Protocol · in the page specification/2025-06-18/client/sampling …t->>User: Present request for approval User-->>Client: Review and approve/modify Note over Client,LLM: Model interaction Client->>LLM: Forward approved request LLM-->>Client: Return g… Specification Model Context Protocol · in the page specification/2025-06-18/index …zing its use 4. **LLM Sampling Controls** * Users must explicitly approve any LLM sampling requests * Users should control: * Whether sampling occurs at all * The actual prompt that w… Schema Reference Model Context Protocol · in the page specification/2025-06-18/schema …them to inspect the request (human in the loop) and decide whether to approve it.</p> </div> <section class="tsd-panel tsd-member"> <div class="tsd-anchor-link" id="createmessagerequest-method" data-t… Authorization Model Context Protocol · in the page specification/2025-11-25/basic/authorization …->>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redirect_uri Client->>Server: Exchange code for token<br/>… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …ient may present request to user C->>U: Review request U->>C: Approve request Note over C,LLM: Client may involve LLM C->>LLM: Request completion LLM->>C: Return completion N… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …nse actions are: 1. **Accept** (`action: "accept"`): User explicitly approved and submitted with data * For form mode: The `content` field contains the submitted data matching the requested schema… Sampling Model Context Protocol · in the page specification/2025-11-25/client/sampling …w Client->>User: Present request for approval User-->>Client: Approve/modify Client->>LLM: Forward request with tools LLM-->>Client: Response with tool_use<br/>(stopReason: "toolUse")… Specification Model Context Protocol · in the page specification/2025-11-25/index …zing its use 4. **LLM Sampling Controls** * Users must explicitly approve any LLM sampling requests * Users should control: * Whether sampling occurs at all * The actual prompt that w… Client Registration Model Context Protocol · in the page specification/2026-07-28/basic/authorization/client-registration …->>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redirect_uri Client->>Server: Exchange code for token<br/>… Elicitation Model Context Protocol · in the page specification/2026-07-28/client/elicitation …nse actions are: 1. **Accept** (`action: "accept"`): User explicitly approved and submitted with data * For form mode: The `content` field contains the submitted data matching the requested schema… Sampling Model Context Protocol · in the page specification/2026-07-28/client/sampling …w Client->>User: Present request for approval User-->>Client: Approve/modify Client->>LLM: Forward request with tools LLM-->>Client: Response with tool_use<br/>(stopReason: "toolUse")… Client Registration Model Context Protocol · in the page specification/draft/basic/authorization/client-registration …->>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redirect_uri Client->>Server: Exchange code for token<br/>… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …nse actions are: 1. **Accept** (`action: "accept"`): User explicitly approved and submitted with data * For form mode: The `content` field contains the submitted data matching the requested schema… Sampling Model Context Protocol · in the page specification/draft/client/sampling …w Client->>User: Present request for approval User-->>Client: Approve/modify Client->>LLM: Forward request with tools LLM-->>Client: Response with tool_use<br/>(stopReason: "toolUse")…