name draft revision draft

dsp-ant · dsp-ant · commit 7b12e988bf2f · 2025-01-08T14:34:37.000Z
diff --git a/docs/specification/draft/basic/_index.md b/docs/specification/draft/basic/_index.md
@@ -6,7 +6,7 @@ weight: 2
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 All messages between MCP clients and servers **MUST** follow the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines three fundamental types of messages:
diff --git a/docs/specification/draft/basic/lifecycle.md b/docs/specification/draft/basic/lifecycle.md
@@ -5,7 +5,7 @@ weight: 30
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server connections that ensures proper capability negotiation and state management.
diff --git a/docs/specification/draft/basic/messages.md b/docs/specification/draft/basic/messages.md
@@ -4,7 +4,7 @@ type: docs
 weight: 20
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 All messages in MCP **MUST** follow the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines three types of messages:
diff --git a/docs/specification/draft/basic/transports.md b/docs/specification/draft/basic/transports.md
@@ -1,10 +1,10 @@
 ---
 title: Transports
 type: docs
-weight: 40
+weight: 10
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 MCP currently defines two standard transport mechanisms for client-server communication:
diff --git a/docs/specification/draft/basic/utilities/_index.md b/docs/specification/draft/basic/utilities/_index.md
@@ -3,7 +3,7 @@ title: Utilities
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 These optional features enhance the base protocol functionality with various utilities.
diff --git a/docs/specification/draft/basic/utilities/cancellation.md b/docs/specification/draft/basic/utilities/cancellation.md
@@ -4,7 +4,7 @@ weight: 10
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) supports optional cancellation of in-progress requests through notification messages. Either side can send a cancellation notification to indicate that a previously-issued request should be terminated.
diff --git a/docs/specification/draft/basic/utilities/ping.md b/docs/specification/draft/basic/utilities/ping.md
@@ -4,7 +4,7 @@ weight: 5
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol includes an optional ping mechanism that allows either party to verify that their counterpart is still responsive and the connection is alive.
diff --git a/docs/specification/draft/basic/utilities/progress.md b/docs/specification/draft/basic/utilities/progress.md
@@ -3,7 +3,7 @@ title: Progress
 weight: 30
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) supports optional progress tracking for long-running operations through notification messages. Either side can send progress notifications to provide updates about operation status.
diff --git a/docs/specification/draft/basic/versioning.md b/docs/specification/draft/basic/versioning.md
@@ -6,7 +6,7 @@ weight: 80
 
 The Model Context Protocol uses string-based version identifiers following the format `YYYY-MM-DD`, to indicate the last date backwards incompatible changes were made.
 
-The current protocol version is **{{< param protocolRevision >}}**. [See all revisions]({{< ref "/specification/draft/revisions" >}}).
+The current protocol version is **draft**. [See all revisions]({{< ref "/specification/draft/revisions" >}}).
 
 {{< callout type="info" >}}
   The protocol version will _not_ be incremented when the protocol is updated, as long as the changes maintain backwards compatibility. This allows for incremental improvements while preserving interoperability.
diff --git a/docs/specification/draft/client/_index.md b/docs/specification/draft/client/_index.md
@@ -6,7 +6,7 @@ weight: 4
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 Clients can implement additional features to enrich connected MCP servers:
diff --git a/docs/specification/draft/client/roots.md b/docs/specification/draft/client/roots.md
@@ -5,7 +5,7 @@ weight: 40
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for clients to expose filesystem "roots" to servers. Roots define the boundaries of where servers can operate within the filesystem, allowing them to understand which directories and files they have access to. Servers can request the list of roots from supporting clients and receive notifications when that list changes.
diff --git a/docs/specification/draft/client/sampling.md b/docs/specification/draft/client/sampling.md
@@ -5,7 +5,7 @@ weight: 40
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to request LLM sampling ("completions" or "generations") from language models via clients. This flow allows clients to maintain control over model access, selection, and permissions while enabling servers to leverage AI capabilities&mdash;with no server API keys necessary. Servers can request text or image-based interactions and optionally include context from MCP servers in their prompts.
diff --git a/docs/specification/draft/server/_index.md b/docs/specification/draft/server/_index.md
@@ -6,7 +6,7 @@ weight: 3
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 Servers provide the fundamental building blocks for adding context to language models via MCP. These primitives enable rich interactions between clients, servers, and language models:
diff --git a/docs/specification/draft/server/prompts.md b/docs/specification/draft/server/prompts.md
@@ -4,7 +4,7 @@ weight: 10
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt templates to clients. Prompts allow servers to provide structured messages and instructions for interacting with language models. Clients can discover available prompts, retrieve their contents, and provide arguments to customize them.
diff --git a/docs/specification/draft/server/resources.md b/docs/specification/draft/server/resources.md
@@ -5,7 +5,7 @@ weight: 20
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose resources to clients. Resources allow servers to share data that provides context to language models, such as files, database schemas, or application-specific information. Each resource is uniquely identified by a [URI](https://datatracker.ietf.org/doc/html/rfc3986).
diff --git a/docs/specification/draft/server/tools.md b/docs/specification/draft/server/tools.md
@@ -5,7 +5,7 @@ weight: 40
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) allows servers to expose tools that can be invoked by language models. Tools enable models to interact with external systems, such as querying databases, calling APIs, or performing computations. Each tool is uniquely identified by a name and includes metadata describing its schema.
diff --git a/docs/specification/draft/server/utilities/_index.md b/docs/specification/draft/server/utilities/_index.md
@@ -3,7 +3,7 @@ title: Utilities
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 These optional features can be used to enhance server functionality.
diff --git a/docs/specification/draft/server/utilities/completion.md b/docs/specification/draft/server/utilities/completion.md
@@ -3,7 +3,7 @@ title: Completion
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to offer argument autocompletion suggestions for prompts and resource URIs. This enables rich, IDE-like experiences where users receive contextual suggestions while entering argument values.
diff --git a/docs/specification/draft/server/utilities/logging.md b/docs/specification/draft/server/utilities/logging.md
@@ -3,7 +3,7 @@ title: Logging
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to send structured log messages to clients. Clients can control logging verbosity by setting minimum log levels, with servers sending notifications containing severity levels, optional logger names, and arbitrary JSON-serializable data.
diff --git a/docs/specification/draft/server/utilities/pagination.md b/docs/specification/draft/server/utilities/pagination.md
@@ -2,7 +2,7 @@
 title: Pagination
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: {{< param protocolRevision >}}
+**Protocol Revision**: draft
 {{< /callout >}}
 
 The Model Context Protocol (MCP) supports paginating list operations that may return large result sets. Pagination allows servers to yield results in smaller chunks rather than all at once.
