One read of Model Context Protocolmcp-20261020T200724Z
306 pages moved out of 357 read.
Pages moved
306
significant first
Pages read
357
in this capture
Captured
20:07 UTC
Corpus hash
077a51951f96
corpus-hash
What this read moved
176-200 of 306, page 8 of 13This capture is too large to show at once. Changes 176-200 of 306 are below, significant first; the rest are on the following screens.
seps/973-expose-additional-metadata-for-implementations-res Changed · +11 / -17 lines
from line 2
22
33> Expose additional metadata for Implementations, Resources, Tools and Prompts
44
5<div className="flex items-center gap-2 mb-4">
6 <Badge color="green" shape="pill">
7 Final
8 </Badge>
5Final
96
10 <Badge color="gray" shape="pill">
11 Standards Track
12 </Badge>
13</div>
7Standards Track
148
15<Note>
16 This SEP has reached Final status and is preserved as a historical record of
17 the design as accepted. Changes made to the protocol after finalization are
18 not reflected here. Refer to the [current
19 specification](/specification/latest) and its changelog for authoritative
20 requirements.
21</Note>
9> [!NOTE]
10>
11> This SEP has reached Final status and is preserved as a historical record of
12> the design as accepted. Changes made to the protocol after finalization are
13> not reflected here. Refer to the [current
14> specification](/specification/latest) and its changelog for authoritative
15> requirements.
2216
2317| Field | Value |
2418| - | - |
from line 37
4337
4438Current implementations only expose namespaced metadata, forcing clients to display generic labels with no visual cues.
4539
46<img width="606" height="242" alt="Image" src="https://github.com/user-attachments/assets/0708a467-ed16-4654-8017-47fc30df9b23" />
40
4741
4842### Proposed State
4943
5044The proposed implementation would allow us to add visual affordances and links to documentation, making it easier to visually identify which servers/clients are providing an implementation e.g. a tool in a slash command interface:
5145
52<img width="1104" height="780" alt="Image" src="https://github.com/user-attachments/assets/2989b847-8a35-4c49-bb73-d27828df4df6" />
46
5347
5448* **Visual Affordance:** Icons make it immediately clear to users which tool or resource source is in use.
5549* **Discoverability:** A link to documentation (`websiteUrl`) allows clients to direct users to more information with a single click.
seps/985-align-oauth-20-protected-resource-metadata-with-rf Changed · +9 / -15 lines
from line 2
22
33> Align OAuth 2.0 Protected Resource Metadata with RFC 9728
44
5<div className="flex items-center gap-2 mb-4">
6 <Badge color="green" shape="pill">
7 Final
8 </Badge>
5Final
96
10 <Badge color="gray" shape="pill">
11 Standards Track
12 </Badge>
13</div>
7Standards Track
148
15<Note>
16 This SEP has reached Final status and is preserved as a historical record of
17 the design as accepted. Changes made to the protocol after finalization are
18 not reflected here. Refer to the [current
19 specification](/specification/latest) and its changelog for authoritative
20 requirements.
21</Note>
9> [!NOTE]
10>
11> This SEP has reached Final status and is preserved as a historical record of
12> the design as accepted. Changes made to the protocol after finalization are
13> not reflected here. Refer to the [current
14> specification](/specification/latest) and its changelog for authoritative
15> requirements.
2216
2317| Field | Value |
2418| - | - |
seps/986-specify-format-for-tool-names Changed · +9 / -15 lines
from line 2
22
33> Specify Format for Tool Names
44
5<div className="flex items-center gap-2 mb-4">
6 <Badge color="green" shape="pill">
7 Final
8 </Badge>
5Final
96
10 <Badge color="gray" shape="pill">
11 Standards Track
12 </Badge>
13</div>
7Standards Track
148
15<Note>
16 This SEP has reached Final status and is preserved as a historical record of
17 the design as accepted. Changes made to the protocol after finalization are
18 not reflected here. Refer to the [current
19 specification](/specification/latest) and its changelog for authoritative
20 requirements.
21</Note>
9> [!NOTE]
10>
11> This SEP has reached Final status and is preserved as a historical record of
12> the design as accepted. Changes made to the protocol after finalization are
13> not reflected here. Refer to the [current
14> specification](/specification/latest) and its changelog for authoritative
15> requirements.
2216
2317| Field | Value |
2418| - | - |
seps/990-enable-enterprise-idp-policy-controls-during-mcp-o Changed · +11 / -16 lines
from line 2
22
33> Enable enterprise IdP policy controls during MCP OAuth flows
44
5<div className="flex items-center gap-2 mb-4">
6 <Badge color="green" shape="pill">
7 Final
8 </Badge>
5Final
96
10 <Badge color="gray" shape="pill">
11 Standards Track
12 </Badge>
13</div>
7Standards Track
148
15<Note>
16 This SEP has reached Final status and is preserved as a historical record of
17 the design as accepted. Changes made to the protocol after finalization are
18 not reflected here. Refer to the [current
19 specification](/specification/latest) and its changelog for authoritative
20 requirements.
21</Note>
9> [!NOTE]
10>
11> This SEP has reached Final status and is preserved as a historical record of
12> the design as accepted. Changes made to the protocol after finalization are
13> not reflected here. Refer to the [current
14> specification](/specification/latest) and its changelog for authoritative
15> requirements.
2216
2317| Field | Value |
2418| - | - |
from line 85
9185 end
9286```
9387
94> \[!IMPORTANT]
88> [!IMPORTANT]
89>
9590> **State:** Ready to Review
9691
seps/991-enable-url-based-client-registration-using-oauth-c Changed · +11 / -17 lines
from line 2
22
33> Enable URL-based Client Registration using OAuth Client ID Metadata Documents
44
5<div className="flex items-center gap-2 mb-4">
6 <Badge color="green" shape="pill">
7 Final
8 </Badge>
5Final
96
10 <Badge color="gray" shape="pill">
11 Standards Track
12 </Badge>
13</div>
7Standards Track
148
15<Note>
16 This SEP has reached Final status and is preserved as a historical record of
17 the design as accepted. Changes made to the protocol after finalization are
18 not reflected here. Refer to the [current
19 specification](/specification/latest) and its changelog for authoritative
20 requirements.
21</Note>
9> [!NOTE]
10>
11> This SEP has reached Final status and is preserved as a historical record of
12> the design as accepted. Changes made to the protocol after finalization are
13> not reflected here. Refer to the [current
14> specification](/specification/latest) and its changelog for authoritative
15> requirements.
2216
2317| Field | Value |
2418| - | - |
seps/994-shared-communication-practicesguidelines Changed · +9 / -15 lines
from line 2
22
33> Shared Communication Practices/Guidelines
44
5<div className="flex items-center gap-2 mb-4">
6 <Badge color="green" shape="pill">
7 Final
8 </Badge>
5Final
96
10 <Badge color="gray" shape="pill">
11 Process
12 </Badge>
13</div>
7Process
148
15<Note>
16 This SEP has reached Final status and is preserved as a historical record of
17 the design as accepted. Changes made to the protocol after finalization are
18 not reflected here. Refer to the [current
19 specification](/specification/latest) and its changelog for authoritative
20 requirements.
21</Note>
9> [!NOTE]
10>
11> This SEP has reached Final status and is preserved as a historical record of
12> the design as accepted. Changes made to the protocol after finalization are
13> not reflected here. Refer to the [current
14> specification](/specification/latest) and its changelog for authoritative
15> requirements.
2216
2317| Field | Value |
2418| - | - |
seps/index Changed · +54 / -54 lines
from line 6
66
77Each SEP is reachable by number at `/seps/<number>` (for example, [/seps/1850](/seps/1850)).
88
9<Card title="Submit a SEP" icon="file-plus" href="/community/sep-guidelines">
10 Learn how to submit your own Specification Enhancement Proposal
11</Card>
9> **[Submit a SEP](/community/sep-guidelines)**
10>
11> Learn how to submit your own Specification Enhancement Proposal
1212
1313## Summary
1414
from line 18
1818
1919| SEP | Title | Status | Type | Created |
2020| - | - | - | - | - |
21| [SEP-2663](/seps/2663-tasks-extension) | Tasks Extension | <Badge color="green" shape="pill">Final</Badge> | Extensions Track | 2026-04-27 |
22| [SEP-2640](/seps/2640-skills-extension) | Skills Extension | <Badge color="green" shape="pill">Final</Badge> | Extensions Track | 2026-04-23 |
23| [SEP-2596](/seps/2596-spec-feature-lifecycle-and-deprecation) | Specification Feature Lifecycle and Deprecation Policy | <Badge color="green" shape="pill">Final</Badge> | Process | 2026-04-17 |
24| [SEP-2577](/seps/2577-deprecate-roots-sampling-and-logging) | Deprecate Roots, Sampling, and Logging | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-04-14 |
25| [SEP-2575](/seps/2575-stateless-mcp) | Make MCP Stateless | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-06-18 |
26| [SEP-2567](/seps/2567-sessionless-mcp) | Sessionless MCP via Explicit State Handles | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-03-11 |
27| [SEP-2549](/seps/2549-TTL-for-list-results) | TTL for List Results | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-04-09 |
28| [SEP-2484](/seps/2484-conformance-tests-required-for-final-seps) | Require Conformance Tests for Standards Track SEPs to Reach Final Status | <Badge color="green" shape="pill">Final</Badge> | Process | 2026-03-27 |
29| [SEP-2468](/seps/2468-recommend-issuer-claim-for-auth) | Recommend Issuer (iss) Parameter in MCP Auth Responses | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-03-25 |
30| [SEP-2322](/seps/2322-MRTR) | Multi Round-Trip Requests | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-02-03 |
31| [SEP-2260](/seps/2260-Require-Server-requests-to-be-associated-with-Client-requests) | Require Server requests to be associated with a Client request. | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-02-16 |
32| [SEP-2243](/seps/2243-http-standardization) | HTTP Header Standardization for Streamable HTTP Transport | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-02-04 |
33| [SEP-2207](/seps/2207-oidc-refresh-token-guidance) | OIDC-Flavored Refresh Token Guidance | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-02-04 |
34| [SEP-2164](/seps/2164-resource-not-found-error) | Standardize Resource Not Found Error Code | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-01-28 |
35| [SEP-2149](/seps/2149-working-group-charter-template) | MCP Group Governance and Charter Template | <Badge color="green" shape="pill">Final</Badge> | Process | 2025-01-15 |
36| [SEP-2148](/seps/2148-contributor-ladder) | MCP Contributor Ladder | <Badge color="green" shape="pill">Final</Badge> | Process | 2026-01-15 |
37| [SEP-2133](/seps/2133-extensions) | Extensions | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-01-21 |
38| [SEP-2127](/seps/2127-mcp-server-cards) | MCP Server Cards - HTTP Server Discovery | <Badge color="green" shape="pill">Final</Badge> | Extensions Track | 2026-01-21 |
39| [SEP-2106](/seps/2106-json-schema-2020-12) | Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2026-01-06 |
40| [SEP-2085](/seps/2085-governance-succession-and-amendment) | Governance Succession and Amendment Procedures | <Badge color="green" shape="pill">Final</Badge> | Process | 2025-12-05 |
41| [SEP-1865](/seps/1865-mcp-apps-interactive-user-interfaces-for-mcp) | MCP Apps - Interactive User Interfaces for MCP | <Badge color="green" shape="pill">Final</Badge> | Extensions Track | 2025-11-21 |
42| [SEP-1850](/seps/1850-pr-based-sep-workflow) | PR-Based SEP Workflow | <Badge color="green" shape="pill">Final</Badge> | Process | 2025-11-20 |
43| [SEP-1730](/seps/1730-sdks-tiering-system) | SDKs Tiering System | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-10-29 |
44| [SEP-1699](/seps/1699-support-sse-polling-via-server-side-disconnect) | Support SSE polling via server-side disconnect | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-10-22 |
45| [SEP-1686](/seps/1686-tasks) | Tasks | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-10-20 |
46| [SEP-1613](/seps/1613-establish-json-schema-2020-12-as-default-dialect-f) | Establish JSON Schema 2020-12 as Default Dialect for MCP | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-10-06 |
47| [SEP-1577](/seps/1577--sampling-with-tools) | Sampling With Tools | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-09-30 |
48| [SEP-1330](/seps/1330-elicitation-enum-schema-improvements-and-standards) | Elicitation Enum Schema Improvements and Standards Compliance | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-08-11 |
49| [SEP-1319](/seps/1319-decouple-request-payload-from-rpc-methods-definiti) | Decouple Request Payload from RPC Methods Definition | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-08-08 |
50| [SEP-1303](/seps/1303-input-validation-errors-as-tool-execution-errors) | Input Validation Errors as Tool Execution Errors | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-08-05 |
51| [SEP-1302](/seps/1302-formalize-working-groups-and-interest-groups-in-mc) | Formalize Working Groups and Interest Groups in MCP Governance | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-08-05 |
52| [SEP-1046](/seps/1046-support-oauth-client-credentials-flow-in-authoriza) | Support OAuth client credentials flow in authorization | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-23 |
53| [SEP-1036](/seps/1036-url-mode-elicitation-for-secure-out-of-band-intera) | URL Mode Elicitation for secure out-of-band interactions | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-22 |
54| [SEP-1034](/seps/1034--support-default-values-for-all-primitive-types-in) | Support default values for all primitive types in elicitation schemas | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-22 |
55| [SEP-1024](/seps/1024-mcp-client-security-requirements-for-local-server-) | MCP Client Security Requirements for Local Server Installation | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-22 |
56| [SEP-994](/seps/994-shared-communication-practicesguidelines) | Shared Communication Practices/Guidelines | <Badge color="green" shape="pill">Final</Badge> | Process | 2025-07-17 |
57| [SEP-991](/seps/991-enable-url-based-client-registration-using-oauth-c) | Enable URL-based Client Registration using OAuth Client ID Metadata Documents | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-07 |
58| [SEP-990](/seps/990-enable-enterprise-idp-policy-controls-during-mcp-o) | Enable enterprise IdP policy controls during MCP OAuth flows | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-06-04 |
59| [SEP-986](/seps/986-specify-format-for-tool-names) | Specify Format for Tool Names | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-16 |
60| [SEP-985](/seps/985-align-oauth-20-protected-resource-metadata-with-rf) | Align OAuth 2.0 Protected Resource Metadata with RFC 9728 | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-16 |
61| [SEP-973](/seps/973-expose-additional-metadata-for-implementations-res) | Expose additional metadata for Implementations, Resources, Tools and Prompts | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-07-15 |
62| [SEP-932](/seps/932-model-context-protocol-governance) | Model Context Protocol Governance | <Badge color="green" shape="pill">Final</Badge> | Process | 2025-07-08 |
63| [SEP-414](/seps/414-request-meta) | Document OpenTelemetry Trace Context Propagation Conventions | <Badge color="green" shape="pill">Final</Badge> | Standards Track | 2025-04-25 |
21| [SEP-2663](/seps/2663-tasks-extension) | Tasks Extension | Final | Extensions Track | 2026-04-27 |
22| [SEP-2640](/seps/2640-skills-extension) | Skills Extension | Final | Extensions Track | 2026-04-23 |
23| [SEP-2596](/seps/2596-spec-feature-lifecycle-and-deprecation) | Specification Feature Lifecycle and Deprecation Policy | Final | Process | 2026-04-17 |
24| [SEP-2577](/seps/2577-deprecate-roots-sampling-and-logging) | Deprecate Roots, Sampling, and Logging | Final | Standards Track | 2026-04-14 |
25| [SEP-2575](/seps/2575-stateless-mcp) | Make MCP Stateless | Final | Standards Track | 2025-06-18 |
26| [SEP-2567](/seps/2567-sessionless-mcp) | Sessionless MCP via Explicit State Handles | Final | Standards Track | 2026-03-11 |
27| [SEP-2549](/seps/2549-TTL-for-list-results) | TTL for List Results | Final | Standards Track | 2026-04-09 |
28| [SEP-2484](/seps/2484-conformance-tests-required-for-final-seps) | Require Conformance Tests for Standards Track SEPs to Reach Final Status | Final | Process | 2026-03-27 |
29| [SEP-2468](/seps/2468-recommend-issuer-claim-for-auth) | Recommend Issuer (iss) Parameter in MCP Auth Responses | Final | Standards Track | 2026-03-25 |
30| [SEP-2322](/seps/2322-MRTR) | Multi Round-Trip Requests | Final | Standards Track | 2026-02-03 |
31| [SEP-2260](/seps/2260-Require-Server-requests-to-be-associated-with-Client-requests) | Require Server requests to be associated with a Client request. | Final | Standards Track | 2026-02-16 |
32| [SEP-2243](/seps/2243-http-standardization) | HTTP Header Standardization for Streamable HTTP Transport | Final | Standards Track | 2026-02-04 |
33| [SEP-2207](/seps/2207-oidc-refresh-token-guidance) | OIDC-Flavored Refresh Token Guidance | Final | Standards Track | 2026-02-04 |
34| [SEP-2164](/seps/2164-resource-not-found-error) | Standardize Resource Not Found Error Code | Final | Standards Track | 2026-01-28 |
35| [SEP-2149](/seps/2149-working-group-charter-template) | MCP Group Governance and Charter Template | Final | Process | 2025-01-15 |
36| [SEP-2148](/seps/2148-contributor-ladder) | MCP Contributor Ladder | Final | Process | 2026-01-15 |
37| [SEP-2133](/seps/2133-extensions) | Extensions | Final | Standards Track | 2025-01-21 |
38| [SEP-2127](/seps/2127-mcp-server-cards) | MCP Server Cards - HTTP Server Discovery | Final | Extensions Track | 2026-01-21 |
39| [SEP-2106](/seps/2106-json-schema-2020-12) | Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 | Final | Standards Track | 2026-01-06 |
40| [SEP-2085](/seps/2085-governance-succession-and-amendment) | Governance Succession and Amendment Procedures | Final | Process | 2025-12-05 |
41| [SEP-1865](/seps/1865-mcp-apps-interactive-user-interfaces-for-mcp) | MCP Apps - Interactive User Interfaces for MCP | Final | Extensions Track | 2025-11-21 |
42| [SEP-1850](/seps/1850-pr-based-sep-workflow) | PR-Based SEP Workflow | Final | Process | 2025-11-20 |
43| [SEP-1730](/seps/1730-sdks-tiering-system) | SDKs Tiering System | Final | Standards Track | 2025-10-29 |
44| [SEP-1699](/seps/1699-support-sse-polling-via-server-side-disconnect) | Support SSE polling via server-side disconnect | Final | Standards Track | 2025-10-22 |
45| [SEP-1686](/seps/1686-tasks) | Tasks | Final | Standards Track | 2025-10-20 |
46| [SEP-1613](/seps/1613-establish-json-schema-2020-12-as-default-dialect-f) | Establish JSON Schema 2020-12 as Default Dialect for MCP | Final | Standards Track | 2025-10-06 |
47| [SEP-1577](/seps/1577--sampling-with-tools) | Sampling With Tools | Final | Standards Track | 2025-09-30 |
48| [SEP-1330](/seps/1330-elicitation-enum-schema-improvements-and-standards) | Elicitation Enum Schema Improvements and Standards Compliance | Final | Standards Track | 2025-08-11 |
49| [SEP-1319](/seps/1319-decouple-request-payload-from-rpc-methods-definiti) | Decouple Request Payload from RPC Methods Definition | Final | Standards Track | 2025-08-08 |
50| [SEP-1303](/seps/1303-input-validation-errors-as-tool-execution-errors) | Input Validation Errors as Tool Execution Errors | Final | Standards Track | 2025-08-05 |
51| [SEP-1302](/seps/1302-formalize-working-groups-and-interest-groups-in-mc) | Formalize Working Groups and Interest Groups in MCP Governance | Final | Standards Track | 2025-08-05 |
52| [SEP-1046](/seps/1046-support-oauth-client-credentials-flow-in-authoriza) | Support OAuth client credentials flow in authorization | Final | Standards Track | 2025-07-23 |
53| [SEP-1036](/seps/1036-url-mode-elicitation-for-secure-out-of-band-intera) | URL Mode Elicitation for secure out-of-band interactions | Final | Standards Track | 2025-07-22 |
54| [SEP-1034](/seps/1034--support-default-values-for-all-primitive-types-in) | Support default values for all primitive types in elicitation schemas | Final | Standards Track | 2025-07-22 |
55| [SEP-1024](/seps/1024-mcp-client-security-requirements-for-local-server-) | MCP Client Security Requirements for Local Server Installation | Final | Standards Track | 2025-07-22 |
56| [SEP-994](/seps/994-shared-communication-practicesguidelines) | Shared Communication Practices/Guidelines | Final | Process | 2025-07-17 |
57| [SEP-991](/seps/991-enable-url-based-client-registration-using-oauth-c) | Enable URL-based Client Registration using OAuth Client ID Metadata Documents | Final | Standards Track | 2025-07-07 |
58| [SEP-990](/seps/990-enable-enterprise-idp-policy-controls-during-mcp-o) | Enable enterprise IdP policy controls during MCP OAuth flows | Final | Standards Track | 2025-06-04 |
59| [SEP-986](/seps/986-specify-format-for-tool-names) | Specify Format for Tool Names | Final | Standards Track | 2025-07-16 |
60| [SEP-985](/seps/985-align-oauth-20-protected-resource-metadata-with-rf) | Align OAuth 2.0 Protected Resource Metadata with RFC 9728 | Final | Standards Track | 2025-07-16 |
61| [SEP-973](/seps/973-expose-additional-metadata-for-implementations-res) | Expose additional metadata for Implementations, Resources, Tools and Prompts | Final | Standards Track | 2025-07-15 |
62| [SEP-932](/seps/932-model-context-protocol-governance) | Model Context Protocol Governance | Final | Process | 2025-07-08 |
63| [SEP-414](/seps/414-request-meta) | Document OpenTelemetry Trace Context Propagation Conventions | Final | Standards Track | 2025-04-25 |
6464
6565## SEP Status Definitions
6666
6767| Status | Definition |
6868| - | - |
69| <Badge color="gray" shape="pill">Draft</Badge> | SEP proposal with a sponsor, undergoing informal review |
70| <Badge color="yellow" shape="pill">In-Review</Badge> | SEP proposal ready for formal review by Core Maintainers |
71| <Badge color="blue" shape="pill">Accepted</Badge> | SEP accepted, awaiting reference implementation |
72| <Badge color="green" shape="pill">Final</Badge> | SEP finalized with reference implementation complete |
73| <Badge color="red" shape="pill">Rejected</Badge> | SEP rejected by Core Maintainers |
74| <Badge color="red" shape="pill">Withdrawn</Badge> | SEP withdrawn by the author |
75| <Badge color="purple" shape="pill">Superseded</Badge> | SEP replaced by a newer SEP |
76| <Badge color="orange" shape="pill">Dormant</Badge> | SEP without a sponsor, closed after 6 months |
69| Draft | SEP proposal with a sponsor, undergoing informal review |
70| In-Review | SEP proposal ready for formal review by Core Maintainers |
71| Accepted | SEP accepted, awaiting reference implementation |
72| Final | SEP finalized with reference implementation complete |
73| Rejected | SEP rejected by Core Maintainers |
74| Withdrawn | SEP withdrawn by the author |
75| Superseded | SEP replaced by a newer SEP |
76| Dormant | SEP without a sponsor, closed after 6 months |
7777
specification/2024-11-05/basic/index Changed · +6 / -8 lines
from line 35
3535
3636See the following pages for more details on the different components:
3737
38<CardGroup cols={3}>
39 <Card title="Lifecycle" icon="arrows-rotate" href="/specification/2024-11-05/basic/lifecycle" />
38> **[Lifecycle](/specification/2024-11-05/basic/lifecycle)**
4039
41 <Card title="Resources" icon="file-lines" href="/specification/2024-11-05/server/resources" />
40> **[Resources](/specification/2024-11-05/server/resources)**
4241
43 <Card title="Prompts" icon="message" href="/specification/2024-11-05/server/prompts" />
42> **[Prompts](/specification/2024-11-05/server/prompts)**
4443
45 <Card title="Tools" icon="wrench" href="/specification/2024-11-05/server/tools" />
44> **[Tools](/specification/2024-11-05/server/tools)**
4645
47 <Card title="Logging" icon="rectangle-list" href="/specification/2024-11-05/server/utilities/logging" />
46> **[Logging](/specification/2024-11-05/server/utilities/logging)**
4847
49 <Card title="Sampling" icon="code" href="/specification/2024-11-05/client/sampling" />
50</CardGroup>
48> **[Sampling](/specification/2024-11-05/client/sampling)**
5149
5250## Auth
5351
specification/2024-11-05/client/sampling Changed · +10 / -10 lines
from line 16
1616their needs—the protocol itself does not mandate any specific user interaction
1717model.
1818
19<Warning>
20 For trust & safety and security, there **SHOULD** always
21 be a human in the loop with the ability to deny sampling requests.
22
23 Applications **SHOULD**:
24
25 * Provide UI that makes it easy and intuitive to review sampling requests
26 * Allow users to view and edit prompts before sending
27 * Present generated responses for review before delivery
28</Warning>
19> [!WARNING]
20>
21> For trust & safety and security, there **SHOULD** always
22> be a human in the loop with the ability to deny sampling requests.
23>
24> Applications **SHOULD**:
25>
26> * Provide UI that makes it easy and intuitive to review sampling requests
27> * Allow users to view and edit prompts before sending
28> * Present generated responses for review before delivery
2929
3030## Capabilities
3131
specification/2024-11-05/index Changed · +5 / -7 lines
from line 116
116116
117117Explore the detailed specification for each protocol component:
118118
119<CardGroup cols={5}>
120 <Card title="Architecture" icon="sitemap" href="/specification/2024-11-05/architecture" />
119> **[Architecture](/specification/2024-11-05/architecture)**
121120
122 <Card title="Base Protocol" icon="code" href="/specification/2024-11-05/basic" />
121> **[Base Protocol](/specification/2024-11-05/basic)**
123122
124 <Card title="Server Features" icon="server" href="/specification/2024-11-05/server" />
123> **[Server Features](/specification/2024-11-05/server)**
125124
126 <Card title="Client Features" icon="user" href="/specification/2024-11-05/client" />
125> **[Client Features](/specification/2024-11-05/client)**
127126
128 <Card title="Contributing" icon="pencil" href="/community/contributing" />
129</CardGroup>
127> **[Contributing](/community/contributing)**
130128
specification/2024-11-05/server/index Changed · +3 / -5 lines
from line 20
2020
2121Explore these key primitives in more detail below:
2222
23<CardGroup cols={3}>
24 <Card title="Prompts" icon="message" href="/specification/2024-11-05/server/prompts" />
23> **[Prompts](/specification/2024-11-05/server/prompts)**
2524
26 <Card title="Resources" icon="file-lines" href="/specification/2024-11-05/server/resources" />
25> **[Resources](/specification/2024-11-05/server/resources)**
2726
28 <Card title="Tools" icon="wrench" href="/specification/2024-11-05/server/tools" />
29</CardGroup>
27> **[Tools](/specification/2024-11-05/server/tools)**
3028
specification/2024-11-05/server/tools Changed · +11 / -11 lines
from line 15
1515suits their needs—the protocol itself does not mandate any specific user
1616interaction model.
1717
18<Warning>
19 For trust & safety and security, there **SHOULD** always
20 be a human in the loop with the ability to deny tool invocations.
21
22 Applications **SHOULD**:
23
24 * Provide UI that makes clear which tools are being exposed to the AI model
25 * Insert clear visual indicators when tools are invoked
26 * Present confirmation prompts to the user for operations, to ensure a human is in the
27 loop
28</Warning>
18> [!WARNING]
19>
20> For trust & safety and security, there **SHOULD** always
21> be a human in the loop with the ability to deny tool invocations.
22>
23> Applications **SHOULD**:
24>
25> * Provide UI that makes clear which tools are being exposed to the AI model
26> * Insert clear visual indicators when tools are invoked
27> * Present confirmation prompts to the user for operations, to ensure a human is in the
28> loop
2929
3030## Capabilities
3131
specification/2025-03-26/basic/transports Changed · +6 / -6 lines
from line 47
4747
4848## Streamable HTTP
4949
50<Info>
51 This replaces the [HTTP+SSE
52 transport](/specification/2024-11-05/basic/transports#http-with-sse) from
53 protocol version 2024-11-05. See the [backwards compatibility](#backwards-compatibility)
54 guide below.
55</Info>
50> [!NOTE]
51>
52> This replaces the [HTTP+SSE
53> transport](/specification/2024-11-05/basic/transports#http-with-sse) from
54> protocol version 2024-11-05. See the [backwards compatibility](#backwards-compatibility)
55> guide below.
5656
5757In the **Streamable HTTP** transport, the server operates as an independent process that
5858can handle multiple client connections. This transport uses HTTP POST and GET requests.
specification/2025-03-26/client/sampling Changed · +10 / -10 lines
from line 16
1616their needs—the protocol itself does not mandate any specific user interaction
1717model.
1818
19<Warning>
20 For trust & safety and security, there **SHOULD** always
21 be a human in the loop with the ability to deny sampling requests.
22
23 Applications **SHOULD**:
24
25 * Provide UI that makes it easy and intuitive to review sampling requests
26 * Allow users to view and edit prompts before sending
27 * Present generated responses for review before delivery
28</Warning>
19> [!WARNING]
20>
21> For trust & safety and security, there **SHOULD** always
22> be a human in the loop with the ability to deny sampling requests.
23>
24> Applications **SHOULD**:
25>
26> * Provide UI that makes it easy and intuitive to review sampling requests
27> * Allow users to view and edit prompts before sending
28> * Present generated responses for review before delivery
2929
3030## Capabilities
3131
specification/2025-03-26/index Changed · +5 / -7 lines
from line 118
118118
119119Explore the detailed specification for each protocol component:
120120
121<CardGroup cols={5}>
122 <Card title="Architecture" icon="sitemap" href="/specification/2025-03-26/architecture" />
121> **[Architecture](/specification/2025-03-26/architecture)**
123122
124 <Card title="Base Protocol" icon="code" href="/specification/2025-03-26/basic" />
123> **[Base Protocol](/specification/2025-03-26/basic)**
125124
126 <Card title="Server Features" icon="server" href="/specification/2025-03-26/server" />
125> **[Server Features](/specification/2025-03-26/server)**
127126
128 <Card title="Client Features" icon="user" href="/specification/2025-03-26/client" />
127> **[Client Features](/specification/2025-03-26/client)**
129128
130 <Card title="Contributing" icon="pencil" href="/community/contributing" />
131</CardGroup>
129> **[Contributing](/community/contributing)**
132130
specification/2025-03-26/server/index Changed · +3 / -5 lines
from line 20
2020
2121Explore these key primitives in more detail below:
2222
23<CardGroup cols={3}>
24 <Card title="Prompts" icon="message" href="/specification/2025-03-26/server/prompts" />
23> **[Prompts](/specification/2025-03-26/server/prompts)**
2524
26 <Card title="Resources" icon="file-lines" href="/specification/2025-03-26/server/resources" />
25> **[Resources](/specification/2025-03-26/server/resources)**
2726
28 <Card title="Tools" icon="wrench" href="/specification/2025-03-26/server/tools" />
29</CardGroup>
27> **[Tools](/specification/2025-03-26/server/tools)**
3028
specification/2025-03-26/server/tools Changed · +15 / -15 lines
from line 15
1515suits their needs—the protocol itself does not mandate any specific user
1616interaction model.
1717
18<Warning>
19 For trust & safety and security, there **SHOULD** always
20 be a human in the loop with the ability to deny tool invocations.
18> [!WARNING]
19>
20> For trust & safety and security, there **SHOULD** always
21> be a human in the loop with the ability to deny tool invocations.
22>
23> Applications **SHOULD**:
24>
25> * Provide UI that makes clear which tools are being exposed to the AI model
26> * Insert clear visual indicators when tools are invoked
27> * Present confirmation prompts to the user for operations, to ensure a human is in the
28> loop
2129
22 Applications **SHOULD**:
23
24 * Provide UI that makes clear which tools are being exposed to the AI model
25 * Insert clear visual indicators when tools are invoked
26 * Present confirmation prompts to the user for operations, to ensure a human is in the
27 loop
28</Warning>
29
3030## Capabilities
3131
3232Servers that support tools **MUST** declare the `tools` capability:
from line 179
179179* `inputSchema`: JSON Schema defining expected parameters
180180* `annotations`: optional properties describing tool behavior
181181
182<Warning>
183 For trust & safety and security, clients **MUST** consider
184 tool annotations to be untrusted unless they come from trusted servers.
185</Warning>
182> [!WARNING]
183>
184> For trust & safety and security, clients **MUST** consider
185> tool annotations to be untrusted unless they come from trusted servers.
186186
187187### Tool Result
188188
specification/2025-06-18/basic/lifecycle Changed · +5 / -7 lines
from line 1
11# Lifecycle
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server
64connections that ensures proper capability negotiation and state management.
75
from line 130
132130If the client does not support the version in the server's response, it **SHOULD**
133131disconnect.
134132
135<Note>
136 If using HTTP, the client **MUST** include the `MCP-Protocol-Version: <protocol-version>` HTTP header on all subsequent requests to the MCP
137 server.
138 For details, see [the Protocol Version Header section in Transports](/specification/2025-06-18/basic/transports#protocol-version-header).
139</Note>
133> [!NOTE]
134>
135> If using HTTP, the client **MUST** include the `MCP-Protocol-Version: <protocol-version>` HTTP header on all subsequent requests to the MCP
136> server.
137> For details, see [the Protocol Version Header section in Transports](/specification/2025-06-18/basic/transports#protocol-version-header).
140138
141139#### Capability Negotiation
142140
specification/2025-06-18/basic/transports Changed · +6 / -8 lines
from line 1
11# Transports
22
3<div id="enable-section-numbers" />
4
53MCP uses JSON-RPC to encode messages. JSON-RPC messages **MUST** be UTF-8 encoded.
64
75The protocol currently defines two standard transport mechanisms for client-server
from line 45
4745
4846## Streamable HTTP
4947
50<Info>
51 This replaces the [HTTP+SSE
52 transport](/specification/2024-11-05/basic/transports#http-with-sse) from
53 protocol version 2024-11-05. See the [backwards compatibility](#backwards-compatibility)
54 guide below.
55</Info>
48> [!NOTE]
49>
50> This replaces the [HTTP+SSE
51> transport](/specification/2024-11-05/basic/transports#http-with-sse) from
52> protocol version 2024-11-05. See the [backwards compatibility](#backwards-compatibility)
53> guide below.
5654
5755In the **Streamable HTTP** transport, the server operates as an independent process that
5856can handle multiple client connections. This transport uses HTTP POST and GET requests.
specification/2025-06-18/client/elicitation Changed · +14 / -16 lines
from line 1
11# Elicitation
22
3<div id="enable-section-numbers" />
3> [!NOTE]
4>
5> Elicitation is newly introduced in this version of the MCP specification and its design may evolve in future protocol versions.
46
5<Note>
6 Elicitation is newly introduced in this version of the MCP specification and its design may evolve in future protocol versions.
7</Note>
8
97The Model Context Protocol (MCP) provides a standardized way for servers to request additional
108information from users through the client during interactions. This flow allows clients to
119maintain control over user interactions and data sharing while enabling servers to gather
from line 19
2119their needs—the protocol itself does not mandate any specific user interaction
2220model.
2321
24<Warning>
25 For trust & safety and security:
26
27 * Servers **MUST NOT** use elicitation to request sensitive information.
28
29 Applications **SHOULD**:
30
31 * Provide UI that makes it clear which server is requesting information
32 * Allow users to review and modify their responses before sending
33 * Respect user privacy and provide clear decline and cancel options
34</Warning>
22> [!WARNING]
23>
24> For trust & safety and security:
25>
26> * Servers **MUST NOT** use elicitation to request sensitive information.
27>
28> Applications **SHOULD**:
29>
30> * Provide UI that makes it clear which server is requesting information
31> * Allow users to review and modify their responses before sending
32> * Respect user privacy and provide clear decline and cancel options
3533
3634## Capabilities
3735
specification/2025-06-18/client/sampling Changed · +10 / -12 lines
from line 1
11# Sampling
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) provides a standardized way for servers to request LLM
64sampling ("completions" or "generations") from language models via clients. This flow
75allows clients to maintain control over model access, selection, and permissions while
from line 16
1816their needs—the protocol itself does not mandate any specific user interaction
1917model.
2018
21<Warning>
22 For trust & safety and security, there **SHOULD** always
23 be a human in the loop with the ability to deny sampling requests.
24
25 Applications **SHOULD**:
26
27 * Provide UI that makes it easy and intuitive to review sampling requests
28 * Allow users to view and edit prompts before sending
29 * Present generated responses for review before delivery
30</Warning>
19> [!WARNING]
20>
21> For trust & safety and security, there **SHOULD** always
22> be a human in the loop with the ability to deny sampling requests.
23>
24> Applications **SHOULD**:
25>
26> * Provide UI that makes it easy and intuitive to review sampling requests
27> * Allow users to view and edit prompts before sending
28> * Present generated responses for review before delivery
3129
3230## Capabilities
3331
specification/2025-06-18/index Changed · +5 / -9 lines
from line 1
11# Specification
22
3<div id="enable-section-numbers" />
4
53[Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open protocol that
64enables seamless integration between LLM applications and external data sources and
75tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating
from line 120
122120
123121Explore the detailed specification for each protocol component:
124122
125<CardGroup cols={5}>
126 <Card title="Architecture" icon="sitemap" href="/specification/2025-06-18/architecture" />
123> **[Architecture](/specification/2025-06-18/architecture)**
127124
128 <Card title="Base Protocol" icon="code" href="/specification/2025-06-18/basic" />
125> **[Base Protocol](/specification/2025-06-18/basic)**
129126
130 <Card title="Server Features" icon="server" href="/specification/2025-06-18/server" />
127> **[Server Features](/specification/2025-06-18/server)**
131128
132 <Card title="Client Features" icon="user" href="/specification/2025-06-18/client" />
129> **[Client Features](/specification/2025-06-18/client)**
133130
134 <Card title="Contributing" icon="pencil" href="/community/contributing" />
135</CardGroup>
131> **[Contributing](/community/contributing)**
136132
specification/2025-06-18/server/index Changed · +3 / -5 lines
from line 20
2020
2121Explore these key primitives in more detail below:
2222
23<CardGroup cols={3}>
24 <Card title="Prompts" icon="message" href="/specification/2025-06-18/server/prompts" />
23> **[Prompts](/specification/2025-06-18/server/prompts)**
2524
26 <Card title="Resources" icon="file-lines" href="/specification/2025-06-18/server/resources" />
25> **[Resources](/specification/2025-06-18/server/resources)**
2726
28 <Card title="Tools" icon="wrench" href="/specification/2025-06-18/server/tools" />
29</CardGroup>
27> **[Tools](/specification/2025-06-18/server/tools)**
3028
specification/2025-06-18/server/prompts Changed · +6 / -8 lines
from line 1
11# Prompts
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt
64templates to clients. Prompts allow servers to provide structured messages and
75instructions for interacting with language models. Clients can discover available
from line 15
1715
1816For example, as slash commands:
1917
20<img src="https://mintcdn.com/mcp/4ZXF1PrDkEaJvXpn/specification/2025-06-18/server/slash-command.png?fit=max&auto=format&n=4ZXF1PrDkEaJvXpn&q=85&s=7f003e36d881dd6f3e5b8cbdd85e5ca5" alt="Example of prompt exposed as slash command" width="293" height="106" data-path="specification/2025-06-18/server/slash-command.png" />
18
2119
2220However, implementors are free to expose prompts through any interface pattern that suits
2321their needs—the protocol itself does not mandate any specific user interaction
from line 180
182180* `role`: Either "user" or "assistant" to indicate the speaker
183181* `content`: One of the following content types:
184182
185<Note>
186 All content types in prompt messages support optional
187 [annotations](/specification/2025-06-18/server/resources#annotations) for
188 metadata about audience, priority, and modification times.
189</Note>
183> [!NOTE]
184>
185> All content types in prompt messages support optional
186> [annotations](/specification/2025-06-18/server/resources#annotations) for
187> metadata about audience, priority, and modification times.
190188
191189#### Text Content
192190
specification/2025-06-18/server/tools Changed · +30 / -32 lines
from line 1
11# Tools
22
3<div id="enable-section-numbers" />
4
53The Model Context Protocol (MCP) allows servers to expose tools that can be invoked by
64language models. Tools enable models to interact with external systems, such as querying
75databases, calling APIs, or performing computations. Each tool is uniquely identified by
from line 15
1715suits their needs—the protocol itself does not mandate any specific user
1816interaction model.
1917
20<Warning>
21 For trust & safety and security, there **SHOULD** always
22 be a human in the loop with the ability to deny tool invocations.
18> [!WARNING]
19>
20> For trust & safety and security, there **SHOULD** always
21> be a human in the loop with the ability to deny tool invocations.
22>
23> Applications **SHOULD**:
24>
25> * Provide UI that makes clear which tools are being exposed to the AI model
26> * Insert clear visual indicators when tools are invoked
27> * Present confirmation prompts to the user for operations, to ensure a human is in the
28> loop
2329
24 Applications **SHOULD**:
25
26 * Provide UI that makes clear which tools are being exposed to the AI model
27 * Insert clear visual indicators when tools are invoked
28 * Present confirmation prompts to the user for operations, to ensure a human is in the
29 loop
30</Warning>
31
3230## Capabilities
3331
3432Servers that support tools **MUST** declare the `tools` capability:
from line 182
184182* `outputSchema`: Optional JSON Schema defining expected output structure
185183* `annotations`: optional properties describing tool behavior
186184
187<Warning>
188 For trust & safety and security, clients **MUST** consider
189 tool annotations to be untrusted unless they come from trusted servers.
190</Warning>
185> [!WARNING]
186>
187> For trust & safety and security, clients **MUST** consider
188> tool annotations to be untrusted unless they come from trusted servers.
191189
192190### Tool Result
193191
from line 193
195193
196194**Unstructured** content is returned in the `content` field of a result, and can contain multiple content items of different types:
197195
198<Note>
199 All content types (text, image, audio, resource links, and embedded resources)
200 support optional
201 [annotations](/specification/2025-06-18/server/resources#annotations) that
202 provide metadata about audience, priority, and modification times. This is the
203 same annotation format used by resources and prompts.
204</Note>
196> [!NOTE]
197>
198> All content types (text, image, audio, resource links, and embedded resources)
199> support optional
200> [annotations](/specification/2025-06-18/server/resources#annotations) that
201> provide metadata about audience, priority, and modification times. This is the
202> same annotation format used by resources and prompts.
205203
206204#### Text Content
207205
from line 257
259257
260258Resource links support the same [Resource annotations](/specification/2025-06-18/server/resources#annotations) as regular resources to help clients understand how to use them.
261259
262<Info>
263 Resource links returned by tools are not guaranteed to appear in the results
264 of a `resources/list` request.
265</Info>
260> [!NOTE]
261>
262> Resource links returned by tools are not guaranteed to appear in the results
263> of a `resources/list` request.
266264
267265#### Embedded Resources
268266
from line 291
293291
294292For backwards compatibility, a tool that returns structured content SHOULD also return the serialized JSON in a TextContent block.
295293
296<Note>
297 `structuredContent` is server-produced result data and is unrelated to LLM
298 "structured outputs" (schema-constrained model generation).
299</Note>
294> [!NOTE]
295>
296> `structuredContent` is server-produced result data and is unrelated to LLM
297> "structured outputs" (schema-constrained model generation).
300298
301299#### Output Schema
302300