449 pages for domain.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
Build with Agent Skills
Model Context Protocol · in the page
docs/2026-07-28/develop/build-with-agent-skills
…io/home) are portable instruction sets that give AI coding assistants domain knowledge for a task. For MCP development, they encode the design decisions (deployment model, tool patterns, auth) so your…
Client Best Practices
Model Context Protocol · in the page
docs/2026-07-28/develop/clients/client-best-practices
…doesn't offer one or when you need specialized retrieval logic (e.g., domain-specific ranking or access-control filtering). The three-layer pattern below illustrates a custom search-based approach in…
Understanding MCP servers
Model Context Protocol · in the page
docs/2026-07-28/learn/server-concepts
…They allow MCP server authors to provide parameterized prompts for a domain, or showcase how to best use the MCP server. #### How Prompts Work Prompts are structured templates that define expected…
Configuration and flags
Model Context Protocol · in the page
docs/2026-07-28/tools/inspector/configuration
…Port of the app-origin server used by MCP Apps that declare `_meta.ui.domain`. Defaults to `6278`; `0` asks the OS. | | `MCP_SANDBOX_FULL_ADDRESS` | Public URL of the MCP Apps sandbox proxy, for runni…
Recipes
Model Context Protocol · in the page
docs/2026-07-28/tools/inspector/recipes
…get_pros", "resourceUri": "ui://pros/view.html", "csp": { "connectDomains": ["https://api.example.com"] }, "permissions": { "clipboard": false }, "prefersBorder": true, "resourceMimeType": "…
Web client
Model Context Protocol · in the page
docs/2026-07-28/tools/inspector/web
…with `MCP_SANDBOX_PORT`). An app whose UI resource declares `_meta.ui.domain` has its document served from a third listener, the app origin, on `6278` by default (`MCP_APP_ORIGIN_PORT`). Expose or for…
Local Server Security
Model Context Protocol · in the page
docs/2026-07-28/tutorials/security/local-server-security
…important assumption: **the client and a stdio server share one trust domain.** They run side by side with the same privileges, and neither the protocol nor the SDKs defend one against the other — a s…
Security Best Practices
Model Context Protocol · in the page
docs/2026-07-28/tutorials/security/security_best_practices
…local services (Redis, databases, admin panels) * **DNS rebinding**: Domains that change DNS resolution between validation and use (e.g., `https://attacker.com` resolving to a safe IP initially,…
Build with Agent Skills
Model Context Protocol · in the page
docs/draft/develop/build-with-agent-skills
…io/home) are portable instruction sets that give AI coding assistants domain knowledge for a task. For MCP development, they encode the design decisions (deployment model, tool patterns, auth) so your…
Client Best Practices
Model Context Protocol · in the page
docs/draft/develop/clients/client-best-practices
…doesn't offer one or when you need specialized retrieval logic (e.g., domain-specific ranking or access-control filtering). The three-layer pattern below illustrates a custom search-based approach in…
Understanding MCP servers
Model Context Protocol · in the page
docs/draft/learn/server-concepts
…They allow MCP server authors to provide parameterized prompts for a domain, or showcase how to best use the MCP server. #### How Prompts Work Prompts are structured templates that define expected…
Configuration and flags
Model Context Protocol · in the page
docs/draft/tools/inspector/configuration
…Port of the app-origin server used by MCP Apps that declare `_meta.ui.domain`. Defaults to `6278`; `0` asks the OS. | | `MCP_SANDBOX_FULL_ADDRESS` | Public URL of the MCP Apps sandbox proxy, for runni…
Recipes
Model Context Protocol · in the page
docs/draft/tools/inspector/recipes
…get_pros", "resourceUri": "ui://pros/view.html", "csp": { "connectDomains": ["https://api.example.com"] }, "permissions": { "clipboard": false }, "prefersBorder": true, "resourceMimeType": "…
Web client
Model Context Protocol · in the page
docs/draft/tools/inspector/web
…with `MCP_SANDBOX_PORT`). An app whose UI resource declares `_meta.ui.domain` has its document served from a third listener, the app origin, on `6278` by default (`MCP_APP_ORIGIN_PORT`). Expose or for…
Local Server Security
Model Context Protocol · in the page
docs/draft/tutorials/security/local-server-security
…important assumption: **the client and a stdio server share one trust domain.** They run side by side with the same privileges, and neither the protocol nor the SDKs defend one against the other — a s…
Security Best Practices
Model Context Protocol · in the page
docs/draft/tutorials/security/security_best_practices
…local services (Redis, databases, admin panels) * **DNS rebinding**: Domains that change DNS resolution between validation and use (e.g., `https://attacker.com` resolving to a safe IP initially,…
Extensions Overview
Model Context Protocol · in the page
extensions/overview
…[!TIP] > > If you're building a third-party extension, use a reversed domain name you own as the vendor prefix to avoid collisions (similar to Java package naming). For example, a company owning `exam…
The MCP Registry
Model Context Protocol · in the page
registry/about
…r `com.example/server`) that ties them to verified GitHub accounts or domains. This namespace system ensures that only the legitimate owner of a GitHub account or domain can publish servers under tha…
How to Authenticate When Publishing to the Official MCP Registry
Model Context Protocol · in the page
registry/authentication
…me/*`). For example, `io.github.alice/weather-server`. If you choose domain-based authentication, your server's name in `server.json` **MUST** be of the form `com.example.*/*`, where `com.example` is…
How to Automate Publishing with GitHub Actions
Model Context Protocol · in the page
registry/github-actions
…!!!!!!!!!!!!!!!!!!!!!!! # TODO: Replace `example.com` with your domain name # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - name: Authenticate to MCP Registry…
MCP Registry Supported Package Types
Model Context Protocol · in the page
registry/package-types
…iner Registry (`ghcr.io`) * Google Artifact Registry (any `*.pkg.dev` domain) * Azure Container Registry (`*.azurecr.io`) * Microsoft Container Registry (`mcr.microsoft.com`) Docker/OCI images use `"…
Quickstart: Publish an MCP Server to the MCP Registry
Model Context Protocol · in the page
registry/quickstart
…(/registry/authentication.md#dns-authentication) which enables custom domains for server name prefixes. * Learn how to [automate publishing with GitHub Actions](/registry/github-actions.md).
Official MCP Registry Terms of Service
Model Context Protocol · in the page
registry/terms-of-service
…ry Data is intended to be public, and will be dedicated to the public domain under [CC0 1.0 Universal](https://creativecommons.org/publicdomain/zero/1.0/). By submitting such data, you agree that you…
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
…Restrictions**: Only HTTPS URLs are allowed for URL elicitation 3. **Domain Validation**: Clients must clearly display target domains to users ### Trust Boundaries URL elicitation explicitly create…
SEP-2127: MCP Server Cards - HTTP Server Discovery
Model Context Protocol · in the page
seps/2127-mcp-server-cards
…RLs for each server, with no standardized discovery mechanism. * **No Domain-Level Discovery**: Clients cannot automatically discover available MCP servers on a domain. This prevents automated integra…
SEP-2133: Extensions
Model Context Protocol · in the page
seps/2133-extensions
…prevent identifier collisions, the vendor prefix SHOULD be a reversed domain name that the extension author owns or controls (similar to Java package naming conventions). For example, a company owning…
SEP-2148: MCP Contributor Ladder
Model Context Protocol · in the page
seps/2148-contributor-ladder
…ecosystem, including enterprise adopters deploying MCP in production domains. **Responsibilities:** * Final technical decision authority for contested or cross-cutting issues * Stewardship of proje…
SEP-2207: OIDC-Flavored Refresh Token Guidance
Model Context Protocol · in the page
seps/2207-oidc-refresh-token-guidance
…step (see Specification) to apply additional restrictions—such as domain allowlists, reputation checks, or verification requirements—rather than solely relying on client metadata claims when…
SEP-2567: Sessionless MCP via Explicit State Handles
Model Context Protocol · in the page
seps/2567-sessionless-mcp
…otocol feature, and servers are free to shape them however fits their domain. The pattern works best when: * **Handles are opaque.** A handle that encodes internal structure (`cart_user42_2026-03-11`…
SEP-2640: Skills Extension
Model Context Protocol · in the page
seps/2640-skills-extension
…organizational prefix. Servers MAY organize skills hierarchically by domain, team, version, or any other axis. In `skill://acme/billing/refunds/SKILL.md`, the prefix is `acme/billing` and the skill's…
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
…MUST takes steps to ensure URLs serving icons are from the * same domain as the client/server or a trusted domain. * * Consumers MUST take appropriate precautions when consuming SVGs as they…
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
…an trust clients they've never seen before** based on: * The HTTPS domain hosting the metadata * The metadata content itself * Domain reputation and security policies 2. **Servers maintain f…
Authorization
Model Context Protocol · in the page
specification/2025-03-26/basic/authorization
…orization endpoints are consistently located at the root level of the domain hosting the MCP server, regardless of any path components in the MCP server URL. #### Fallbacks for Servers without Metada…
Schema Reference
Model Context Protocol · in the page
specification/2025-06-18/schema
…human-readable and easily understood, even by those unfamiliar with domain-specific terminology.</p> <p>If not provided, the name should be used for display (except for Tool, where <code>annotatio…
Authorization
Model Context Protocol · in the page
specification/2025-11-25/basic/authorization
…uri in allowed list<br/>3. Document structure valid<br/>4. (Optional) Domain allowed via trust policy alt Validation Success Server->>User: Display consent page with client_name U…
Elicitation
Model Context Protocol · in the page
specification/2025-11-25/client/elicitation
…responses before sending > * For URL mode, clearly display the target domain/host and gather user consent before navigation to the target URL ## Capabilities Clients that support elicitation **MUST*…
Schema Reference
Model Context Protocol · in the page
specification/2025-11-25/schema
…s SHOULD takes steps to ensure URLs serving icons are from the same domain as the client/server or a trusted domain.</p> <p>Consumers SHOULD take appropriate precautions when consuming SVGs as they…
Client Registration
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/client-registration
…uri in allowed list<br/>3. Document structure valid<br/>4. (Optional) Domain allowed via trust policy alt Validation Success Server->>User: Display consent page with client_name U…
Authorization Security Considerations
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/security-considerations
…rization ### Trust Policies Authorization servers **MAY** implement domain-based trust policies for accepting Client ID Metadata Documents, as described in [Section 6.4](https://www.ietf.org/archive…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/index
…sports that run over a reliable bidirectional byte stream (e.g., Unix domain sockets or TCP) **SHOULD** reuse the [stdio framing](/specification/2026-07-28/basic/transports/stdio.md) rather than defin…
stdio
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/stdio
…over a reliable bidirectional byte stream) works unchanged over Unix domain sockets, TCP connections, or any similar channel. [Custom transports](/specification/2026-07-28/basic/transports.md#custom-…
Elicitation
Model Context Protocol · in the page
specification/2026-07-28/client/elicitation
…responses before sending > * For URL mode, clearly display the target domain/host and gather user consent before navigation to the target URL ## Capabilities Clients that support elicitation **MUST*…
Schema Reference
Model Context Protocol · in the page
specification/2026-07-28/schema
…rs SHOULD take steps to ensure URLs serving icons are from the same domain as the client/server or a trusted domain.</p> <p>Consumers SHOULD take appropriate precautions when consuming SVGs as they…
Client Registration
Model Context Protocol · in the page
specification/draft/basic/authorization/client-registration
…uri in allowed list<br/>3. Document structure valid<br/>4. (Optional) Domain allowed via trust policy alt Validation Success Server->>User: Display consent page with client_name U…
Authorization Security Considerations
Model Context Protocol · in the page
specification/draft/basic/authorization/security-considerations
…rization ### Trust Policies Authorization servers **MAY** implement domain-based trust policies for accepting Client ID Metadata Documents, as described in [Section 6.4](https://www.ietf.org/archive…
Overview
Model Context Protocol · in the page
specification/draft/basic/transports/index
…sports that run over a reliable bidirectional byte stream (e.g., Unix domain sockets or TCP) **SHOULD** reuse the [stdio framing](/specification/draft/basic/transports/stdio.md) rather than defining a…
stdio
Model Context Protocol · in the page
specification/draft/basic/transports/stdio
…over a reliable bidirectional byte stream) works unchanged over Unix domain sockets, TCP connections, or any similar channel. [Custom transports](/specification/draft/basic/transports.md#custom-trans…
Elicitation
Model Context Protocol · in the page
specification/draft/client/elicitation
…responses before sending > * For URL mode, clearly display the target domain/host and gather user consent before navigation to the target URL ## Capabilities Clients that support elicitation **MUST*…
Schema Reference
Model Context Protocol · in the page
specification/draft/schema
…rs SHOULD take steps to ensure URLs serving icons are from the same domain as the client/server or a trusted domain.</p> <p>Consumers SHOULD take appropriate precautions when consuming SVGs as they…