Add automatic section numbers via CSS

jonathanhefner · bhosmer-ant · commit 009478fdc811 · 2025-06-07T01:43:52.000-04:00
This adds CSS to automatically generate section numbers based on
headings.  Section numbers are displayed both in headings and in table
of contents links.  Section numbers are opt-in per page, and can be
enabled by including an element with `id="enable-section-numbers"`
anywhere on the page.
diff --git a/docs/specification/2024-11-05/architecture/index.mdx b/docs/specification/2024-11-05/architecture/index.mdx
@@ -2,6 +2,8 @@
 title: Architecture
 ---
 
+<div id="enable-section-numbers" />
+
 The Model Context Protocol (MCP) follows a client-host-server architecture where each
 host can run multiple client instances. This architecture enables users to integrate AI
 capabilities across applications while maintaining clear security boundaries and
diff --git a/docs/specification/2024-11-05/basic/lifecycle.mdx b/docs/specification/2024-11-05/basic/lifecycle.mdx
@@ -4,6 +4,8 @@ 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,6 +4,8 @@ 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,6 +3,8 @@ 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,6 +3,8 @@ 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,6 +3,8 @@ 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,6 +4,8 @@ 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,6 +4,8 @@ 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,6 +3,8 @@ 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,6 +4,8 @@ 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,6 +4,8 @@ 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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/architecture/index.mdx b/docs/specification/2025-03-26/architecture/index.mdx
@@ -2,6 +2,8 @@
 title: Architecture
 ---
 
+<div id="enable-section-numbers" />
+
 The Model Context Protocol (MCP) follows a client-host-server architecture where each
 host can run multiple client instances. This architecture enables users to integrate AI
 capabilities across applications while maintaining clear security boundaries and
diff --git a/docs/specification/2025-03-26/basic/lifecycle.mdx b/docs/specification/2025-03-26/basic/lifecycle.mdx
@@ -2,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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,6 +2,8 @@
 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/architecture/index.mdx b/docs/specification/draft/architecture/index.mdx
@@ -2,6 +2,8 @@
 title: Architecture
 ---
 
+<div id="enable-section-numbers" />
+
 The Model Context Protocol (MCP) follows a client-host-server architecture where each
 host can run multiple client instances. This architecture enables users to integrate AI
 capabilities across applications while maintaining clear security boundaries and
diff --git a/docs/specification/draft/basic/lifecycle.mdx b/docs/specification/draft/basic/lifecycle.mdx
@@ -2,6 +2,8 @@
 title: Lifecycle
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server
diff --git a/docs/specification/draft/basic/transports.mdx b/docs/specification/draft/basic/transports.mdx
@@ -2,6 +2,8 @@
 title: Transports
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 MCP uses JSON-RPC to encode messages. JSON-RPC messages **MUST** be UTF-8 encoded.
diff --git a/docs/specification/draft/basic/utilities/cancellation.mdx b/docs/specification/draft/basic/utilities/cancellation.mdx
@@ -2,6 +2,8 @@
 title: Cancellation
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) supports optional cancellation of in-progress requests
diff --git a/docs/specification/draft/basic/utilities/ping.mdx b/docs/specification/draft/basic/utilities/ping.mdx
@@ -2,6 +2,8 @@
 title: Ping
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol includes an optional ping mechanism that allows either party
diff --git a/docs/specification/draft/basic/utilities/progress.mdx b/docs/specification/draft/basic/utilities/progress.mdx
@@ -2,6 +2,8 @@
 title: Progress
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) supports optional progress tracking for long-running
diff --git a/docs/specification/draft/client/elicitation.mdx b/docs/specification/draft/client/elicitation.mdx
@@ -2,6 +2,8 @@
 title: Elicitation
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 <Note>
diff --git a/docs/specification/draft/client/roots.mdx b/docs/specification/draft/client/roots.mdx
@@ -2,6 +2,8 @@
 title: Roots
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for clients to expose
diff --git a/docs/specification/draft/client/sampling.mdx b/docs/specification/draft/client/sampling.mdx
@@ -2,6 +2,8 @@
 title: Sampling
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to request LLM
diff --git a/docs/specification/draft/server/prompts.mdx b/docs/specification/draft/server/prompts.mdx
@@ -2,6 +2,8 @@
 title: Prompts
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt
diff --git a/docs/specification/draft/server/resources.mdx b/docs/specification/draft/server/resources.mdx
@@ -2,6 +2,8 @@
 title: Resources
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose
diff --git a/docs/specification/draft/server/tools.mdx b/docs/specification/draft/server/tools.mdx
@@ -2,6 +2,8 @@
 title: Tools
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) allows servers to expose tools that can be invoked by
diff --git a/docs/specification/draft/server/utilities/completion.mdx b/docs/specification/draft/server/utilities/completion.mdx
@@ -2,6 +2,8 @@
 title: Completion
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to offer
diff --git a/docs/specification/draft/server/utilities/logging.mdx b/docs/specification/draft/server/utilities/logging.mdx
@@ -2,6 +2,8 @@
 title: Logging
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) provides a standardized way for servers to send
diff --git a/docs/specification/draft/server/utilities/pagination.mdx b/docs/specification/draft/server/utilities/pagination.mdx
@@ -2,6 +2,8 @@
 title: Pagination
 ---
 
+<div id="enable-section-numbers" />
+
 <Info>**Protocol Revision**: draft</Info>
 
 The Model Context Protocol (MCP) supports paginating list operations that may return
diff --git a/docs/style.css b/docs/style.css
