1,313 pages for user.

Versioning and Compatibility Model Context Protocol · in the page specification/draft/basic/versioning …he `supported` list and retry the request, or surface an error to the user if no compatible version exists. Servers **MUST** implement [`server/discover`](/specification/draft/server/discover). Clien… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …a standardized way for servers to request additional information from users through the client during interactions. This flow allows clients to maintain control over user interactions and data sharing… Roots Model Context Protocol · in the page specification/draft/client/roots …s. Servers can request the list of roots from supporting clients. ## User Interaction Model Roots in MCP are typically exposed through workspace or project configuration interfaces. For example, im… Sampling Model Context Protocol · in the page specification/draft/client/sampling …and optionally include context from MCP servers in their prompts. ## User Interaction Model Sampling in MCP allows servers to implement agentic behaviors, by enabling LLM calls to occur *nested* ins… Specification Model Context Protocol · in the page specification/draft/index …wing features to clients: * **Resources**: Context and data, for the user or the AI model to use * **Prompts**: Templated messages and workflows for users * **Tools**: Functions for the AI model to e… Schema Reference Model Context Protocol · in the page specification/draft/schema …ies to indicate content useful for multiple audiences (e.g., <code>\["user", "assistant"]</code>).</p> </div></section> <section class="tsd-panel tsd-member"> <div class="tsd-anchor-link" id="annotati… Overview Model Context Protocol · in the page specification/draft/server/index …ive | Control | Description | Example | | - | - | - | - | | Prompts | User-controlled | Interactive templates invoked by user choice | Slash commands, menu options | | Resources | Application-controll… Prompts Model Context Protocol · in the page specification/draft/server/prompts …` fields; see > [`_meta`](/specification/draft/basic/index#meta). ## User Interaction Model Prompts are designed to be **user-controlled**, meaning they are exposed from servers to clients with the… Resources Model Context Protocol · in the page specification/draft/server/resources …` fields; see > [`_meta`](/specification/draft/basic/index#meta). ## User Interaction Model Resources in MCP are designed to be **application-driven**, with host applications determining how to inco… Tools Model Context Protocol · in the page specification/draft/server/tools …` fields; see > [`_meta`](/specification/draft/basic/index#meta). ## User Interaction Model Tools in MCP are designed to be **model-controlled**, meaning that the language model can discover and inv… Caching Model Context Protocol · in the page specification/draft/server/utilities/caching …ue | Meaning | | - | - | | `"public"` | The response does not contain user-specific data. Any client, shared gateway, or caching proxy **MAY** store and serve the cached response to any user. | | `"pr… Completion Model Context Protocol · in the page specification/draft/server/utilities/completion …suggestions for the arguments of prompts and resource templates. When users are filling in argument values for a specific prompt (identified by name) or resource template (identified by URI), servers… Logging Model Context Protocol · in the page specification/draft/server/utilities/logging …els, optional logger names, and arbitrary JSON-serializable data. ## User Interaction Model Implementations are free to expose logging through any interface pattern that suits their needs—the protoc…