653 pages for display.

Roots Model Context Protocol · in the page specification/2024-11-05/client/roots …e current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri": "file:///home/u… Logging Model Context Protocol · in the page specification/2024-11-05/server/utilities/logging …esent log messages in the UI * Implement log filtering/search * Display severity visually * Persist log messages ## Security 1. Log messages **MUST NOT** contain: * Credentials or secret… Cancellation Model Context Protocol · in the page specification/2025-03-26/basic/utilities/cancellation …e request to cancel * An optional reason string that can be logged or displayed ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/cancelled", "params": { "requestId": "123",… Roots Model Context Protocol · in the page specification/2025-03-26/client/roots …e current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri": "file:///home/u… Logging Model Context Protocol · in the page specification/2025-03-26/server/utilities/logging …esent log messages in the UI * Implement log filtering/search * Display severity visually * Persist log messages ## Security 1. Log messages **MUST NOT** contain: * Credentials or secret… Lifecycle Model Context Protocol · in the page specification/2025-06-18/basic/lifecycle …nfo": { "name": "ExampleClient", "title": "Example Client Display Name", "version": "1.0.0" } } } ``` The server **MUST** respond with its own capabilities and information: `… Cancellation Model Context Protocol · in the page specification/2025-06-18/basic/utilities/cancellation …e request to cancel * An optional reason string that can be logged or displayed ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/cancelled", "params": { "requestId": "123",… Key Changes Model Context Protocol · in the page specification/2025-06-18/changelog …elcontextprotocol/pull/598)). 3. Add `title` field for human-friendly display names, so that `name` can be used as a programmatic identifier (PR [#663](https://github.com/modelcontextprotocol/model… Elicitation Model Context Protocol · in the page specification/2025-06-18/client/elicitation …ies": { "propertyName": { "type": "string", "title": "Display Name", "description": "Description of the property" }, "anotherProperty": { "type": "number", "m… Roots Model Context Protocol · in the page specification/2025-06-18/client/roots …e current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri": "file:///home/u… Schema Reference Model Context Protocol · in the page specification/2025-06-18/schema …ent. The client can use annotations to inform how objects are used or displayed</p> </div> <section class="tsd-panel tsd-member"> <div class="tsd-anchor-link" id="annotations-audience" data-typedoc-h=… Prompts Model Context Protocol · in the page specification/2025-06-18/server/prompts …the prompt * `title`: Optional human-readable name of the prompt for display purposes. * `description`: Optional human-readable description * `arguments`: Optional list of arguments for customization… Resources Model Context Protocol · in the page specification/2025-06-18/server/resources …resource. * `title`: Optional human-readable name of the resource for display purposes. * `description`: Optional description * `mimeType`: Optional MIME type * `size`: Optional size in bytes ### Res… Tools Model Context Protocol · in the page specification/2025-06-18/server/tools …for the tool * `title`: Optional human-readable name of the tool for display purposes. * `description`: Human-readable description of functionality * `inputSchema`: JSON Schema defining expected para… Logging Model Context Protocol · in the page specification/2025-06-18/server/utilities/logging …esent log messages in the UI * Implement log filtering/search * Display severity visually * Persist log messages ## Security 1. Log messages **MUST NOT** contain: * Credentials or secret… Authorization Model Context Protocol · in the page specification/2025-11-25/basic/authorization …d via trust policy alt Validation Success Server->>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redir… Overview Model Context Protocol · in the page specification/2025-11-25/basic/index …Visual representation of the tool's functionality * `Prompt`: Icon to display alongside prompt templates * `Resource`: Visual indicator for different resource types Multiple icons can be provided to… Lifecycle Model Context Protocol · in the page specification/2025-11-25/basic/lifecycle …nfo": { "name": "ExampleClient", "title": "Example Client Display Name", "version": "1.0.0", "description": "An example MCP client application", "icons": [ {… Cancellation Model Context Protocol · in the page specification/2025-11-25/basic/utilities/cancellation …e request to cancel * An optional reason string that can be logged or displayed ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/cancelled", "params": { "requestId": "123",… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …or was cancelled. This allows requestors to monitor status changes or display progress updates while the task executes, even after invoking `tasks/result`. **Request:** ```json theme={null} { "jso… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …w and modify their 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… Roots Model Context Protocol · in the page specification/2025-11-25/client/roots …e current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri": "file:///home/u… Schema Reference Model Context Protocol · in the page specification/2025-11-25/schema …ent. The client can use annotations to inform how objects are used or displayed</p> </div> <section class="tsd-panel tsd-member"> <div class="tsd-anchor-link" id="annotations-audience" data-typedoc-h=… Prompts Model Context Protocol · in the page specification/2025-11-25/server/prompts …the prompt * `title`: Optional human-readable name of the prompt for display purposes. * `description`: Optional human-readable description * `icons`: Optional array of icons for display in user inte… Resources Model Context Protocol · in the page specification/2025-11-25/server/resources …resource. * `title`: Optional human-readable name of the resource for display purposes. * `description`: Optional description * `icons`: Optional array of icons for display in user interfaces * `mimeT… Tools Model Context Protocol · in the page specification/2025-11-25/server/tools …for the tool * `title`: Optional human-readable name of the tool for display purposes. * `description`: Human-readable description of functionality * `icons`: Optional array of icons for display in u… Logging Model Context Protocol · in the page specification/2025-11-25/server/utilities/logging …esent log messages in the UI * Implement log filtering/search * Display severity visually * Persist log messages ## Security 1. Log messages **MUST NOT** contain: * Credentials or secret… Client Registration Model Context Protocol · in the page specification/2026-07-28/basic/authorization/client-registration …d via trust policy alt Validation Success Server->>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redir… Authorization Model Context Protocol · in the page specification/2026-07-28/basic/authorization/index …ly to error responses - on mismatch the client **MUST NOT** act on or display `error`, `error_description`, or `error_uri`. ## Resource Parameter Implementation MCP clients **MUST** implement Resour… Authorization Security Considerations Model Context Protocol · in the page specification/2026-07-28/basic/authorization/security-considerations …RL impersonation by themselves. Authorization servers: * **SHOULD** display additional warnings for `localhost`-only redirect URIs * **MAY** require additional attestation mechanisms for enhanced se… Overview Model Context Protocol · in the page specification/2026-07-28/basic/index …sender and are not verified by the protocol. They are > intended for display, logging, and debugging. Implementations **SHOULD NOT** > use them to change the behavior of the client or server, and **S… Cancellation Model Context Protocol · in the page specification/2026-07-28/basic/patterns/cancellation …e request to cancel * An optional reason string that can be logged or displayed ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/cancelled", "params": { "requestId": "123",… Elicitation Model Context Protocol · in the page specification/2026-07-28/client/elicitation …w and modify their 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… Roots Model Context Protocol · in the page specification/2026-07-28/client/roots …e current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri": "file:///home/u… Schema Reference Model Context Protocol · in the page specification/2026-07-28/schema …ent. The client can use annotations to inform how objects are used or displayed</p> </div> <section class="tsd-panel tsd-member"> <div class="tsd-anchor-link" id="annotations-audience" data-typedoc-h=… Discovery Model Context Protocol · in the page specification/2026-07-28/server/discover …the server and is not verified by the > protocol. It is intended for display, logging, and debugging. Clients **SHOULD > NOT** use it to change their behavior, and **SHOULD NOT** rely on it for > sec… Prompts Model Context Protocol · in the page specification/2026-07-28/server/prompts …the prompt * `title`: Optional human-readable name of the prompt for display purposes. * `description`: Optional human-readable description * `icons`: Optional array of icons for display in user inte… Resources Model Context Protocol · in the page specification/2026-07-28/server/resources …resource. * `title`: Optional human-readable name of the resource for display purposes. * `description`: Optional description * `icons`: Optional array of icons for display in user interfaces * `mimeT… Tools Model Context Protocol · in the page specification/2026-07-28/server/tools …for the tool * `title`: Optional human-readable name of the tool for display purposes. * `description`: Human-readable description of functionality * `icons`: Optional array of icons for display in u… Logging Model Context Protocol · in the page specification/2026-07-28/server/utilities/logging …esent log messages in the UI * Implement log filtering/search * Display severity visually * Persist log messages ## Security 1. Log messages **MUST NOT** contain: * Credentials or secret… Client Registration Model Context Protocol · in the page specification/draft/basic/authorization/client-registration …d via trust policy alt Validation Success Server->>User: Display consent page with client_name User->>Server: Approves access Server->>Client: Authorization code via redir… Authorization Model Context Protocol · in the page specification/draft/basic/authorization/index …ly to error responses - on mismatch the client **MUST NOT** act on or display `error`, `error_description`, or `error_uri`. ## Resource Parameter Implementation MCP clients **MUST** implement Resour… Authorization Security Considerations Model Context Protocol · in the page specification/draft/basic/authorization/security-considerations …RL impersonation by themselves. Authorization servers: * **SHOULD** display additional warnings for `localhost`-only redirect URIs * **MAY** require additional attestation mechanisms for enhanced se… Overview Model Context Protocol · in the page specification/draft/basic/index …sender and are not verified by the protocol. They are > intended for display, logging, and debugging. Implementations **SHOULD NOT** > use them to change the behavior of the client or server, and **S… Cancellation Model Context Protocol · in the page specification/draft/basic/patterns/cancellation …e request to cancel * An optional reason string that can be logged or displayed ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/cancelled", "params": { "requestId": "123",… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …w and modify their 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… Roots Model Context Protocol · in the page specification/draft/client/roots …e current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri": "file:///home/u… Schema Reference Model Context Protocol · in the page specification/draft/schema …ent. The client can use annotations to inform how objects are used or displayed</p> </div> <section class="tsd-panel tsd-member"> <div class="tsd-anchor-link" id="annotations-audience" data-typedoc-h=… Discovery Model Context Protocol · in the page specification/draft/server/discover …the server and is not verified by the > protocol. It is intended for display, logging, and debugging. Clients **SHOULD > NOT** use it to change their behavior, and **SHOULD NOT** rely on it for > sec… Prompts Model Context Protocol · in the page specification/draft/server/prompts …the prompt * `title`: Optional human-readable name of the prompt for display purposes. * `description`: Optional human-readable description * `icons`: Optional array of icons for display in user inte…