1,481 pages for read.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
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
…lient_id`: matching the document URL exactly * `client_name`: human-readable name for authorization prompts * `redirect_uris`: array of allowed redirect URIs * `token_endpoint_auth_method`: "non…
Specification Enhancement Proposals (SEPs)
Model Context Protocol · in the page
seps/index
…th a sponsor, undergoing informal review | | In-Review | SEP proposal ready for formal review by Core Maintainers | | Accepted | SEP accepted, awaiting reference implementation | | Final | SEP finaliz…
Architecture
Model Context Protocol · in the page
specification/2024-11-05/architecture/index
…lar design supports extensibility 3. **Servers should not be able to read the whole conversation, nor "see into" other servers** * Servers receive only necessary contextual information * Ful…
Lifecycle
Model Context Protocol · in the page
specification/2024-11-05/basic/lifecycle
…client **MUST** send an `initialized` notification to indicate it is ready to begin normal operations: ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/initialized" } ``` * The…
Cancellation
Model Context Protocol · in the page
specification/2024-11-05/basic/utilities/cancellation
…ions if: * The referenced request is unknown * Processing has already completed * The request cannot be cancelled 5. The sender of the cancellation notification **SHOULD** ignore any response…
Roots
Model Context Protocol · in the page
specification/2024-11-05/client/roots
…file://` URI in the current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri…
Prompts
Model Context Protocol · in the page
specification/2024-11-05/server/prompts
…me`: Unique identifier for the prompt * `description`: Optional human-readable description * `arguments`: Optional list of arguments for customization ### PromptMessage Messages in a prompt can cont…
Resources
Model Context Protocol · in the page
specification/2024-11-05/server/resources
…t" } ], "nextCursor": "next-page-cursor" } } ``` ### Reading Resources To retrieve resource contents, clients send a `resources/read` request: **Request:** ```json theme={null} {…
Tools
Model Context Protocol · in the page
specification/2024-11-05/server/tools
…des: * `name`: Unique identifier for the tool * `description`: Human-readable description of functionality * `inputSchema`: JSON Schema defining expected parameters ### Tool Result Tool results can…
Architecture
Model Context Protocol · in the page
specification/2025-03-26/architecture/index
…lar design supports extensibility 3. **Servers should not be able to read the whole conversation, nor "see into" other servers** * Servers receive only necessary contextual information * Ful…
Lifecycle
Model Context Protocol · in the page
specification/2025-03-26/basic/lifecycle
…client **MUST** send an `initialized` notification to indicate it is ready to begin normal operations: ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/initialized" } ``` * The…
Transports
Model Context Protocol · in the page
specification/2025-03-26/basic/transports
…: * The client launches the MCP server as a subprocess. * The server reads JSON-RPC messages from its standard input (`stdin`) and sends messages to its standard output (`stdout`). * Messages may b…
Cancellation
Model Context Protocol · in the page
specification/2025-03-26/basic/utilities/cancellation
…ions if: * The referenced request is unknown * Processing has already completed * The request cannot be cancelled 5. The sender of the cancellation notification **SHOULD** ignore any response…
Progress
Model Context Protocol · in the page
specification/2025-03-26/basic/utilities/progress
…oating point. * The `message` field **SHOULD** provide relevant human readable progress information. ## Behavior Requirements 1. Progress notifications **MUST** only reference tokens that: * Were…
Key Changes
Model Context Protocol · in the page
specification/2025-03-26/changelog
…otations** for better describing tool behavior, like whether it is read-only or destructive (PR [#185](https://github.com/modelcontextprotocol/specification/pull/185)) ## Other schema changes…
Roots
Model Context Protocol · in the page
specification/2025-03-26/client/roots
…file://` URI in the current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri…
Prompts
Model Context Protocol · in the page
specification/2025-03-26/server/prompts
…me`: Unique identifier for the prompt * `description`: Optional human-readable description * `arguments`: Optional list of arguments for customization ### PromptMessage Messages in a prompt can cont…
Resources
Model Context Protocol · in the page
specification/2025-03-26/server/resources
…t" } ], "nextCursor": "next-page-cursor" } } ``` ### Reading Resources To retrieve resource contents, clients send a `resources/read` request: **Request:** ```json theme={null} {…
Tools
Model Context Protocol · in the page
specification/2025-03-26/server/tools
…des: * `name`: Unique identifier for the tool * `description`: Human-readable description of functionality * `inputSchema`: JSON Schema defining expected parameters * `annotations`: optional properti…
Architecture
Model Context Protocol · in the page
specification/2025-06-18/architecture/index
…lar design supports extensibility 3. **Servers should not be able to read the whole conversation, nor "see into" other servers** * Servers receive only necessary contextual information * Ful…
Lifecycle
Model Context Protocol · in the page
specification/2025-06-18/basic/lifecycle
…client **MUST** send an `initialized` notification to indicate it is ready to begin normal operations: ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/initialized" } ``` * The…
Transports
Model Context Protocol · in the page
specification/2025-06-18/basic/transports
…: * The client launches the MCP server as a subprocess. * The server reads JSON-RPC messages from its standard input (`stdin`) and sends messages to its standard output (`stdout`). * Messages are i…
Cancellation
Model Context Protocol · in the page
specification/2025-06-18/basic/utilities/cancellation
…ions if: * The referenced request is unknown * Processing has already completed * The request cannot be cancelled 5. The sender of the cancellation notification **SHOULD** ignore any response…
Progress
Model Context Protocol · in the page
specification/2025-06-18/basic/utilities/progress
…oating point. * The `message` field **SHOULD** provide relevant human readable progress information. ## Behavior Requirements 1. Progress notifications **MUST** only reference tokens that: * Were…
Roots
Model Context Protocol · in the page
specification/2025-06-18/client/roots
…file://` URI in the current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri…
Schema Reference
Model Context Protocol · in the page
specification/2025-06-18/schema
…d-comment tsd-typography"><p>A resource that the server is capable of reading, included in a prompt or tool call result.</p> <p>Note: resource links returned by tools are not guaranteed to appear in t…
Prompts
Model Context Protocol · in the page
specification/2025-06-18/server/prompts
…* `name`: Unique identifier for the prompt * `title`: Optional human-readable name of the prompt for display purposes. * `description`: Optional human-readable description * `arguments`: Optional lis…
Resources
Model Context Protocol · in the page
specification/2025-06-18/server/resources
…t" } ], "nextCursor": "next-page-cursor" } } ``` ### Reading Resources To retrieve resource contents, clients send a `resources/read` request: **Request:** ```json theme={null} {…
Tools
Model Context Protocol · in the page
specification/2025-06-18/server/tools
…: * `name`: Unique identifier for the tool * `title`: Optional human-readable name of the tool for display purposes. * `description`: Human-readable description of functionality * `inputSchema`: JSON…
Completion
Model Context Protocol · in the page
specification/2025-06-18/server/utilities/completion
…value * `context`: Object containing: * `arguments`: A mapping of already-resolved argument names to their values. ### CompleteResult * `completion`: Object containing: * `values`: Array of sugg…
Architecture
Model Context Protocol · in the page
specification/2025-11-25/architecture/index
…lar design supports extensibility 3. **Servers should not be able to read the whole conversation, nor "see into" other servers** * Servers receive only necessary contextual information * Ful…
Authorization
Model Context Protocol · in the page
specification/2025-11-25/basic/authorization
…nown/oauth-protected-resource", scope="files:read" ``` MCP clients **MUST** be able to parse `WWW-Authenticate` headers and respond appropriately to `HTTP 401 Unauthorized` r…
Overview
Model Context Protocol · in the page
specification/2025-11-25/basic/index
…t they correspond to (except in error cases where the ID could not be read due a malformed request). * Error responses **MUST** include an `error` field with a `code` and `message`. * Error codes **MU…
Lifecycle
Model Context Protocol · in the page
specification/2025-11-25/basic/lifecycle
…client **MUST** send an `initialized` notification to indicate it is ready to begin normal operations: ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/initialized" } ``` * The…
Transports
Model Context Protocol · in the page
specification/2025-11-25/basic/transports
…: * The client launches the MCP server as a subprocess. * The server reads JSON-RPC messages from its standard input (`stdin`) and sends messages to its standard output (`stdout`). * Messages are i…
Cancellation
Model Context Protocol · in the page
specification/2025-11-25/basic/utilities/cancellation
…ions if: * The referenced request is unknown * Processing has already completed * The request cannot be cancelled 6. The sender of the cancellation notification **SHOULD** ignore any response…
Progress
Model Context Protocol · in the page
specification/2025-11-25/basic/utilities/progress
…oating point. * The `message` field **SHOULD** provide relevant human readable progress information. ## Behavior Requirements 1. Progress notifications **MUST** only reference tokens that: * Were…
Tasks
Model Context Protocol · in the page
specification/2025-11-25/basic/utilities/tasks
…l/related-task` metadata in the result messages, as the `taskId` is already present in the response structure. ### Task Notifications 1. Receivers **MAY** send `notifications/tasks/status` notificat…
Key Changes
Model Context Protocol · in the page
specification/2025-11-25/changelog
…rface to align with MCP registry server.json format and provide human-readable context during initialization. 3. Clarify that servers must respond with HTTP 403 Forbidden for invalid Origin headers in…
Elicitation
Model Context Protocol · in the page
specification/2025-11-25/client/elicitation
…(defaults to `"form"` if omitted). | | `message` | string | | A human-readable message explaining why the interaction is needed. | The `mode` parameter specifies the type of elicitation: * `"form"`:…
Roots
Model Context Protocol · in the page
specification/2025-11-25/client/roots
…file://` URI in the current specification. * `name`: Optional human-readable name for display purposes. Example roots for different use cases: #### Project Directory ```json theme={null} { "uri…
Schema Reference
Model Context Protocol · in the page
specification/2025-11-25/schema
…d-comment tsd-typography"><p>A resource that the server is capable of reading, included in a prompt or tool call result.</p> <p>Note: resource links returned by tools are not guaranteed to appear in t…
Prompts
Model Context Protocol · in the page
specification/2025-11-25/server/prompts
…* `name`: Unique identifier for the prompt * `title`: Optional human-readable name of the prompt for display purposes. * `description`: Optional human-readable description * `icons`: Optional array o…
Resources
Model Context Protocol · in the page
specification/2025-11-25/server/resources
…] } ], "nextCursor": "next-page-cursor" } } ``` ### Reading Resources To retrieve resource contents, clients send a `resources/read` request: **Request:** ```json theme={null} {…
Tools
Model Context Protocol · in the page
specification/2025-11-25/server/tools
…: * `name`: Unique identifier for the tool * `title`: Optional human-readable name of the tool for display purposes. * `description`: Human-readable description of functionality * `icons`: Optional a…
Completion
Model Context Protocol · in the page
specification/2025-11-25/server/utilities/completion
…value * `context`: Object containing: * `arguments`: A mapping of already-resolved argument names to their values. ### CompleteResult * `completion`: Object containing: * `values`: Array of sugg…
Architecture
Model Context Protocol · in the page
specification/2026-07-28/architecture/index
…lar design supports extensibility 3. **Servers should not be able to read the whole conversation, nor "see into" other servers** * Servers receive only necessary contextual information * Ful…
Authorization
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/index
…nown/oauth-protected-resource", scope="files:read" ``` When implementing authorization flows, MCP clients **SHOULD** follow the principle of least privilege by requesting onl…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/index
…t they correspond to (except in error cases where the ID could not be read due a malformed request). * Error responses **MUST** include an `error` field with a `code` and `message`. * Error codes **MU…
Cancellation
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/cancellation
…ions if: * The referenced request is unknown * Processing has already completed * The request cannot be cancelled 5. The client **SHOULD** ignore any response to the cancelled request that ar…