Skip to content

Commit 621ba60

Browse files
jspahrsummersjspahrsummers
committed
Move spec docs out of draft, to new version
1 parent 55d8e5c commit 621ba60

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

50 files changed

+97
-133
lines changed

‎docs/specification/2024-11-05/_index.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,12 @@
11
---
2-
title: Specification (Latest)
2+
title: Specification (2024-11-05)
33
cascade:
44
type: docs
55
breadcrumbs: false
6-
weight: 10
7-
aliases:
8-
- /latest
6+
weight: 2
97
---
108

11-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
12-
{{< /callout >}}
9+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
1310

1411
[Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open protocol that
1512
enables seamless integration between LLM applications and external data sources and

‎docs/specification/2024-11-05/basic/_index.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,7 @@ cascade:
55
weight: 2
66
---
77

8-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
9-
{{< /callout >}}
8+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
109

1110
All messages between MCP clients and servers **MUST** follow the
1211
[JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines

‎docs/specification/2024-11-05/basic/lifecycle.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,7 @@ type: docs
44
weight: 30
55
---
66

7-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
8-
{{< /callout >}}
7+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
98

109
The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server
1110
connections that ensures proper capability negotiation and state management.

‎docs/specification/2024-11-05/basic/messages.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,7 @@ type: docs
44
weight: 20
55
---
66

7-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
8-
{{< /callout >}}
7+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
98

109
All messages in MCP **MUST** follow the
1110
[JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines

‎docs/specification/2024-11-05/basic/transports.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,7 @@ type: docs
44
weight: 40
55
---
66

7-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
8-
{{< /callout >}}
7+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
98

109
MCP currently defines two standard transport mechanisms for client-server communication:
1110

‎docs/specification/2024-11-05/basic/utilities/_index.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,7 @@
22
title: Utilities
33
---
44

5-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
6-
{{< /callout >}}
5+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
76

87
These optional features enhance the base protocol functionality with various utilities.
98

‎docs/specification/2024-11-05/basic/utilities/cancellation.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,7 @@ title: Cancellation
33
weight: 10
44
---
55

6-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
7-
{{< /callout >}}
6+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
87

98
The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
109
through notification messages. Either side can send a cancellation notification to

‎docs/specification/2024-11-05/basic/utilities/ping.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,7 @@ title: Ping
33
weight: 5
44
---
55

6-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
7-
{{< /callout >}}
6+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
87

98
The Model Context Protocol includes an optional ping mechanism that allows either party
109
to verify that their counterpart is still responsive and the connection is alive.

‎docs/specification/2024-11-05/basic/utilities/progress.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,7 @@ title: Progress
33
weight: 30
44
---
55

6-
{{< callout type="info" >}} **Protocol Revision**: {{< param protocolRevision >}}
7-
{{< /callout >}}
6+
{{< callout type="info" >}} **Protocol Revision**: 2024-11-05 {{< /callout >}}
87

98
The Model Context Protocol (MCP) supports optional progress tracking for long-running
109
operations through notification messages. Either side can send progress notifications to

‎docs/specification/2024-11-05/basic/versioning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ weight: 80
77
The Model Context Protocol uses string-based version identifiers following the format
88
`YYYY-MM-DD`, to indicate the last date backwards incompatible changes were made.
99

10-
The current protocol version is **{{< param protocolRevision >}}**. [See all
10+
The current protocol version is **2024-11-05**. [See all
1111
revisions]({{< ref "/specification/2024-11-05/revisions" >}}).
1212

1313
{{< callout type="info" >}} The protocol version will _not_ be incremented when the

0 commit comments

Comments
 (0)