remove section numbers from old spec versions + misc

bhosmer-ant · bhosmer-ant · commit 1589c4424383 · 2025-06-07T01:43:52.000-04:00
diff --git a/docs/specification/2024-11-05/basic/lifecycle.mdx b/docs/specification/2024-11-05/basic/lifecycle.mdx
@@ -4,8 +4,6 @@ type: docs
 weight: 30
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server
diff --git a/docs/specification/2024-11-05/basic/transports.mdx b/docs/specification/2024-11-05/basic/transports.mdx
@@ -4,8 +4,6 @@ type: docs
 weight: 40
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 MCP currently defines two standard transport mechanisms for client-server communication:
diff --git a/docs/specification/2024-11-05/basic/utilities/cancellation.mdx b/docs/specification/2024-11-05/basic/utilities/cancellation.mdx
@@ -3,8 +3,6 @@ title: Cancellation
 weight: 10
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
diff --git a/docs/specification/2024-11-05/basic/utilities/ping.mdx b/docs/specification/2024-11-05/basic/utilities/ping.mdx
@@ -3,8 +3,6 @@ title: Ping
 weight: 5
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol includes an optional ping mechanism that allows either party
diff --git a/docs/specification/2024-11-05/basic/utilities/progress.mdx b/docs/specification/2024-11-05/basic/utilities/progress.mdx
@@ -3,8 +3,6 @@ title: Progress
 weight: 30
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) supports optional progress tracking for long-running
diff --git a/docs/specification/2024-11-05/client/roots.mdx b/docs/specification/2024-11-05/client/roots.mdx
@@ -4,8 +4,6 @@ type: docs
 weight: 40
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for clients to expose
diff --git a/docs/specification/2024-11-05/client/sampling.mdx b/docs/specification/2024-11-05/client/sampling.mdx
@@ -4,8 +4,6 @@ type: docs
 weight: 40
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to request LLM
diff --git a/docs/specification/2024-11-05/server/prompts.mdx b/docs/specification/2024-11-05/server/prompts.mdx
@@ -3,8 +3,6 @@ title: Prompts
 weight: 10
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt
diff --git a/docs/specification/2024-11-05/server/resources.mdx b/docs/specification/2024-11-05/server/resources.mdx
@@ -4,8 +4,6 @@ type: docs
 weight: 20
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose
diff --git a/docs/specification/2024-11-05/server/tools.mdx b/docs/specification/2024-11-05/server/tools.mdx
@@ -4,8 +4,6 @@ type: docs
 weight: 40
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) allows servers to expose tools that can be invoked by
diff --git a/docs/specification/2024-11-05/server/utilities/completion.mdx b/docs/specification/2024-11-05/server/utilities/completion.mdx
@@ -2,8 +2,6 @@
 title: Completion
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to offer
diff --git a/docs/specification/2024-11-05/server/utilities/logging.mdx b/docs/specification/2024-11-05/server/utilities/logging.mdx
@@ -2,8 +2,6 @@
 title: Logging
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to send
diff --git a/docs/specification/2024-11-05/server/utilities/pagination.mdx b/docs/specification/2024-11-05/server/utilities/pagination.mdx
@@ -2,8 +2,6 @@
 title: Pagination
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2024-11-05</Info>
 
 The Model Context Protocol (MCP) supports paginating list operations that may return
diff --git a/docs/specification/2025-03-26/basic/authorization.mdx b/docs/specification/2025-03-26/basic/authorization.mdx
@@ -2,8 +2,6 @@
 title: Authorization
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 ## Introduction
diff --git a/docs/specification/2025-03-26/basic/lifecycle.mdx b/docs/specification/2025-03-26/basic/lifecycle.mdx
@@ -2,8 +2,6 @@
 title: Lifecycle
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server
diff --git a/docs/specification/2025-03-26/basic/transports.mdx b/docs/specification/2025-03-26/basic/transports.mdx
@@ -2,8 +2,6 @@
 title: Transports
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 MCP uses JSON-RPC to encode messages. JSON-RPC messages **MUST** be UTF-8 encoded.
diff --git a/docs/specification/2025-03-26/basic/utilities/cancellation.mdx b/docs/specification/2025-03-26/basic/utilities/cancellation.mdx
@@ -2,8 +2,6 @@
 title: Cancellation
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
diff --git a/docs/specification/2025-03-26/basic/utilities/ping.mdx b/docs/specification/2025-03-26/basic/utilities/ping.mdx
@@ -2,8 +2,6 @@
 title: Ping
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol includes an optional ping mechanism that allows either party
diff --git a/docs/specification/2025-03-26/basic/utilities/progress.mdx b/docs/specification/2025-03-26/basic/utilities/progress.mdx
@@ -2,8 +2,6 @@
 title: Progress
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) supports optional progress tracking for long-running
diff --git a/docs/specification/2025-03-26/client/roots.mdx b/docs/specification/2025-03-26/client/roots.mdx
@@ -2,8 +2,6 @@
 title: Roots
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for clients to expose
diff --git a/docs/specification/2025-03-26/client/sampling.mdx b/docs/specification/2025-03-26/client/sampling.mdx
@@ -2,8 +2,6 @@
 title: Sampling
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to request LLM
diff --git a/docs/specification/2025-03-26/server/prompts.mdx b/docs/specification/2025-03-26/server/prompts.mdx
@@ -2,8 +2,6 @@
 title: Prompts
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt
diff --git a/docs/specification/2025-03-26/server/resources.mdx b/docs/specification/2025-03-26/server/resources.mdx
@@ -2,8 +2,6 @@
 title: Resources
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose
diff --git a/docs/specification/2025-03-26/server/tools.mdx b/docs/specification/2025-03-26/server/tools.mdx
@@ -2,8 +2,6 @@
 title: Tools
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) allows servers to expose tools that can be invoked by
diff --git a/docs/specification/2025-03-26/server/utilities/completion.mdx b/docs/specification/2025-03-26/server/utilities/completion.mdx
@@ -2,8 +2,6 @@
 title: Completion
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to offer
diff --git a/docs/specification/2025-03-26/server/utilities/logging.mdx b/docs/specification/2025-03-26/server/utilities/logging.mdx
@@ -2,8 +2,6 @@
 title: Logging
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to send
diff --git a/docs/specification/2025-03-26/server/utilities/pagination.mdx b/docs/specification/2025-03-26/server/utilities/pagination.mdx
@@ -2,8 +2,6 @@
 title: Pagination
 ---
 
-<div id="enable-section-numbers" />
-
 <Info>**Protocol Revision**: 2025-03-26</Info>
 
 The Model Context Protocol (MCP) supports paginating list operations that may return
diff --git a/docs/specification/draft/changelog.mdx b/docs/specification/draft/changelog.mdx
@@ -2,19 +2,25 @@
 title: Key Changes
 ---
 
+<div id="enable-section-numbers" />
+
 This document lists changes made to the Model Context Protocol (MCP) specification since
 the previous revision, [2025-03-26](/specification/2025-03-26).
 
 ## Major changes
 
 1. Removed support for JSON-RPC **[batching](https://www.jsonrpc.org/specification#batch)**
    (PR [#416](https://github.com/modelcontextprotocol/specification/pull/416))
-2. Added support for [structured tool output](https://modelcontextprotocol.io/specification/draft/server/tools#structured-content)
+2. Added support for [structured tool output](server/tools#structured-content)
    (PR [#371](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/371))
-3. Classified MCP servers as [OAuth Resource Servers](https://modelcontextprotocol.io/specification/draft/basic/authorization#authorization-server-discovery), adding protected resource metadata to discover the corresponding Authorization server. (PR [#338](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/338))
-4. Clarified [security considerations](https://modelcontextprotocol.io/specification/draft/basic/authorization#security-considerations) and best practices in the authorization spec and in a new [security best practices page](https://modelcontextprotocol.io/specification/draft/basic/security_best_practices).
-5. Added support for **[elicitation](/specification/draft/client/elicitation)**, enabling
-   servers to request additional information from users during interactions. (PR [#382](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/382))
+3. Classified MCP servers as [OAuth Resource Servers](basic/authorization#authorization-server-discovery),
+   adding protected resource metadata to discover the corresponding Authorization server.
+   (PR [#338](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/338))
+4. Clarified [security considerations](basic/authorization#security-considerations) and best practices
+   in the authorization spec and in a new [security best practices page](basic/security_best_practices).
+5. Added support for **[elicitation](client/elicitation)**, enabling servers to request additional
+   information from users during interactions.
+   (PR [#382](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/382))
 
 ## Other schema changes
 
diff --git a/docs/specification/draft/index.mdx b/docs/specification/draft/index.mdx
@@ -2,6 +2,8 @@
 title: Specification
 ---
 
+<div id="enable-section-numbers" />
+
 [Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open protocol that
 enables seamless integration between LLM applications and external data sources and
 tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating
