s/2025-03-26/draft/g

Author: pcarleton

docs/specification/draft/architecture/index.mdx

@@ -163,12 +163,12 @@ sequenceDiagram
 Each capability unlocks specific protocol features for use during the session. For
 example:
 
-- Implemented [server features](/specification/2025-03-26/server) must be advertised in the
+- Implemented [server features](/specification/draft/server) must be advertised in the
   server's capabilities
 - Emitting resource subscription notifications requires the server to declare
   subscription support
 - Tool invocation requires the server to declare tool capabilities
-- [Sampling](/specification/2025-03-26/client) requires the client to declare support in its
+- [Sampling](/specification/draft/client) requires the client to declare support in its
   capabilities
 
 This capability negotiation ensures clients and servers have a clear understanding of

docs/specification/draft/basic/authorization.mdx

@@ -2,7 +2,7 @@
 title: Authorization
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 ## 1. Introduction
 

docs/specification/draft/basic/index.mdx

@@ -2,7 +2,7 @@
 title: Overview
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol consists of several key components that work together:
 
@@ -100,7 +100,7 @@ batches, but **MUST** support receiving JSON-RPC batches.
 
 ## Auth
 
-MCP provides an [Authorization](/specification/2025-03-26/basic/authorization) framework for use with HTTP.
+MCP provides an [Authorization](/specification/draft/basic/authorization) framework for use with HTTP.
 Implementations using an HTTP-based transport **SHOULD** conform to this specification,
 whereas implementations using STDIO transport **SHOULD NOT** follow this specification,
 and instead retrieve credentials from the environment.
@@ -116,10 +116,10 @@ to help shape the future of the protocol!
 ## Schema
 
 The full specification of the protocol is defined as a
-[TypeScript schema](https://github.com/modelcontextprotocol/specification/blob/main/schema/2025-03-26/schema.ts).
+[TypeScript schema](https://github.com/modelcontextprotocol/specification/blob/main/schema/draft/schema.ts).
 This is the source of truth for all protocol messages and structures.
 
 There is also a
-[JSON Schema](https://github.com/modelcontextprotocol/specification/blob/main/schema/2025-03-26/schema.json),
+[JSON Schema](https://github.com/modelcontextprotocol/specification/blob/main/schema/draft/schema.json),
 which is automatically generated from the TypeScript source of truth, for use with
 various automated tooling.

docs/specification/draft/basic/lifecycle.mdx

@@ -2,7 +2,7 @@
 title: Lifecycle
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server
 connections that ensures proper capability negotiation and state management.
@@ -118,11 +118,11 @@ to indicate it is ready to begin normal operations:
 ```
 
 - The client **SHOULD NOT** send requests other than
-  [pings](/specification/2025-03-26/basic/utilities/ping) before the server has responded to the
+  [pings](/specification/draft/basic/utilities/ping) before the server has responded to the
   `initialize` request.
 - The server **SHOULD NOT** send requests other than
-  [pings](/specification/2025-03-26/basic/utilities/ping) and
-  [logging](/specification/2025-03-26/server/utilities/logging) before receiving the `initialized`
+  [pings](/specification/draft/basic/utilities/ping) and
+  [logging](/specification/draft/server/utilities/logging) before receiving the `initialized`
   notification.
 
 #### Version Negotiation
@@ -146,13 +146,13 @@ Key capabilities include:
 
 | Category | Capability     | Description                                                                |
 | -------- | -------------- | -------------------------------------------------------------------------- |
-| Client   | `roots`        | Ability to provide filesystem [roots](/specification/2025-03-26/client/roots)       |
-| Client   | `sampling`     | Support for LLM [sampling](/specification/2025-03-26/client/sampling) requests      |
+| Client   | `roots`        | Ability to provide filesystem [roots](/specification/draft/client/roots)       |
+| Client   | `sampling`     | Support for LLM [sampling](/specification/draft/client/sampling) requests      |
 | Client   | `experimental` | Describes support for non-standard experimental features                   |
-| Server   | `prompts`      | Offers [prompt templates](/specification/2025-03-26/server/prompts)                 |
-| Server   | `resources`    | Provides readable [resources](/specification/2025-03-26/server/resources)           |
-| Server   | `tools`        | Exposes callable [tools](/specification/2025-03-26/server/tools)                    |
-| Server   | `logging`      | Emits structured [log messages](/specification/2025-03-26/server/utilities/logging) |
+| Server   | `prompts`      | Offers [prompt templates](/specification/draft/server/prompts)                 |
+| Server   | `resources`    | Provides readable [resources](/specification/draft/server/resources)           |
+| Server   | `tools`        | Exposes callable [tools](/specification/draft/server/tools)                    |
+| Server   | `logging`      | Emits structured [log messages](/specification/draft/server/utilities/logging) |
 | Server   | `experimental` | Describes support for non-standard experimental features                   |
 
 Capability objects can describe sub-capabilities like:
@@ -179,7 +179,7 @@ mechanism should be used to signal connection termination:
 
 #### stdio
 
-For the stdio [transport](/specification/2025-03-26/basic/transports), the client **SHOULD** initiate
+For the stdio [transport](/specification/draft/basic/transports), the client **SHOULD** initiate
 shutdown by:
 
 1. First, closing the input stream to the child process (the server)
@@ -192,22 +192,22 @@ exiting.
 
 #### HTTP
 
-For HTTP [transports](/specification/2025-03-26/basic/transports), shutdown is indicated by closing the
+For HTTP [transports](/specification/draft/basic/transports), shutdown is indicated by closing the
 associated HTTP connection(s).
 
 ## Timeouts
 
 Implementations **SHOULD** establish timeouts for all sent requests, to prevent hung
 connections and resource exhaustion. When the request has not received a success or error
 response within the timeout period, the sender **SHOULD** issue a [cancellation
-notification](/specification/2025-03-26/basic/utilities/cancellation) for that request and stop waiting for
+notification](/specification/draft/basic/utilities/cancellation) for that request and stop waiting for
 a response.
 
 SDKs and other middleware **SHOULD** allow these timeouts to be configured on a
 per-request basis.
 
 Implementations **MAY** choose to reset the timeout clock when receiving a [progress
-notification](/specification/2025-03-26/basic/utilities/progress) corresponding to the request, as this
+notification](/specification/draft/basic/utilities/progress) corresponding to the request, as this
 implies that work is actually happening. However, implementations **SHOULD** always
 enforce a maximum timeout, regardless of progress notifications, to limit the impact of a
 misbehaving client or server.

docs/specification/draft/basic/transports.mdx

@@ -2,7 +2,7 @@
 title: Transports
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 MCP uses JSON-RPC to encode messages. JSON-RPC messages **MUST** be UTF-8 encoded.
 
@@ -178,7 +178,7 @@ act as a cursor within that particular stream.
 ### Session Management
 
 An MCP "session" consists of logically related interactions between a client and a
-server, beginning with the [initialization phase](/specification/2025-03-26/basic/lifecycle). To support
+server, beginning with the [initialization phase](/specification/draft/basic/lifecycle). To support
 servers which want to establish stateful sessions:
 
 1. A server using the Streamable HTTP transport **MAY** assign a session ID at

docs/specification/draft/basic/utilities/cancellation.mdx

@@ -2,7 +2,7 @@
 title: Cancellation
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
 through notification messages. Either side can send a cancellation notification to

docs/specification/draft/basic/utilities/ping.mdx

@@ -2,7 +2,7 @@
 title: Ping
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 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.

docs/specification/draft/basic/utilities/progress.mdx

@@ -2,7 +2,7 @@
 title: Progress
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) supports optional progress tracking for long-running
 operations through notification messages. Either side can send progress notifications to

docs/specification/draft/changelog.mdx

@@ -7,11 +7,11 @@ the previous revision, [2024-11-05](/specification/2024-11-05).
 
 ## Major changes
 
-1. Added a comprehensive **[authorization framework](/specification/2025-03-26/basic/authorization)**
+1. Added a comprehensive **[authorization framework](/specification/draft/basic/authorization)**
    based on OAuth 2.1 (PR
    [#133](https://github.com/modelcontextprotocol/specification/pull/133))
 1. Replaced the previous HTTP+SSE transport with a more flexible **[Streamable HTTP
-   transport](/specification/2025-03-26/basic/transports#streamable-http)** (PR
+   transport](/specification/draft/basic/transports#streamable-http)** (PR
    [#206](https://github.com/modelcontextprotocol/specification/pull/206))
 1. Added support for JSON-RPC **[batching](https://www.jsonrpc.org/specification#batch)**
    (PR [#228](https://github.com/modelcontextprotocol/specification/pull/228))
@@ -27,10 +27,10 @@ the previous revision, [2024-11-05](/specification/2024-11-05).
   autocompletion suggestions
 
 See
-[the updated schema](http://github.com/modelcontextprotocol/specification/tree/main/schema/2025-03-26/schema.ts)
+[the updated schema](http://github.com/modelcontextprotocol/specification/tree/main/schema/draft/schema.ts)
 for more details.
 
 ## Full changelog
 
 For a complete list of all changes that have been made since the last protocol revision,
-[see GitHub](https://github.com/modelcontextprotocol/specification/compare/2024-11-05...2025-03-26).
+[see GitHub](https://github.com/modelcontextprotocol/specification/compare/2024-11-05...draft).

docs/specification/draft/client/roots.mdx

@@ -2,7 +2,7 @@
 title: Roots
 ---
 
-<Info>**Protocol Revision**: 2025-03-26</Info>
+<Info>**Protocol Revision**: draft</Info>
 
 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
@@ -25,7 +25,7 @@ interaction model.
 ## Capabilities
 
 Clients that support roots **MUST** declare the `roots` capability during
-[initialization](/specification/2025-03-26/basic/lifecycle#initialization):
+[initialization](/specification/draft/basic/lifecycle#initialization):
 
 ```json
 {