Rewrite links to spec.modelcontextprotocol.io

Author: jspahrsummers

docs/development/roadmap.mdx

@@ -5,7 +5,7 @@ description: Our plans for evolving Model Context Protocol
 
 <Info>Last updated: **2025-03-27**</Info>
 
-The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and direction for approximately **the next six months**, though these may change significantly as the project develops. To see what's changed recently, check out the **[specification changelog](https://spec.modelcontextprotocol.io/specification/2025-03-26/changelog/)**.
+The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and direction for approximately **the next six months**, though these may change significantly as the project develops. To see what's changed recently, check out the **[specification changelog](/specification/2025-03-26/changelog/)**.
 
 <Note>The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. This is also not an _exhaustive_ list; we may incorporate work that isn't mentioned here.</Note>
 

docs/docs/concepts/architecture.mdx

@@ -109,7 +109,7 @@ The transport layer handles the actual communication between clients and servers
    - Uses Server-Sent Events for server-to-client messages
    - HTTP POST for client-to-server messages
 
-All transports use [JSON-RPC](https://www.jsonrpc.org/) 2.0 to exchange messages. See the [specification](https://spec.modelcontextprotocol.io) for detailed information about the Model Context Protocol message format.
+All transports use [JSON-RPC](https://www.jsonrpc.org/) 2.0 to exchange messages. See the [specification](/specification/) for detailed information about the Model Context Protocol message format.
 
 ### Message types
 

docs/sdk/java/mcp-overview.mdx

@@ -15,12 +15,12 @@ If you're upgrading from 0.7.0, please refer to the [Migration Guide](https://gi
 ## Features
 
 - MCP Client and MCP Server implementations supporting:
-  - Protocol [version compatibility negotiation](https://spec.modelcontextprotocol.io/specification/2024-11-05/basic/lifecycle/#initialization)
-  - [Tool](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/tools/) discovery, execution, list change notifications
-  - [Resource](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/resources/) management with URI templates
-  - [Roots](https://spec.modelcontextprotocol.io/specification/2024-11-05/client/roots/) list management and notifications
-  - [Prompt](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/prompts/) handling and management
-  - [Sampling](https://spec.modelcontextprotocol.io/specification/2024-11-05/client/sampling/) support for AI model interactions
+  - Protocol [version compatibility negotiation](/specification/2024-11-05/basic/lifecycle/#initialization)
+  - [Tool](/specification/2024-11-05/server/tools/) discovery, execution, list change notifications
+  - [Resource](/specification/2024-11-05/server/resources/) management with URI templates
+  - [Roots](/specification/2024-11-05/client/roots/) list management and notifications
+  - [Prompt](/specification/2024-11-05/server/prompts/) handling and management
+  - [Sampling](/specification/2024-11-05/client/sampling/) support for AI model interactions
 - Multiple transport implementations:
   - Default transports (included in core `mcp` module, no external web frameworks required):
     - Stdio-based transport for process-based communication

docs/sdk/java/mcp-server.mdx

@@ -270,7 +270,7 @@ Supported logging levels (in order of increasing severity): DEBUG (0), INFO (1),
 
 ### Tool Specification
 
-The Model Context Protocol allows servers to [expose tools](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/tools/) that can be invoked by language models. 
+The Model Context Protocol allows servers to [expose tools](/specification/2024-11-05/server/tools/) that can be invoked by language models. 
 The Java SDK allows implementing a Tool Specifications with their handler functions. 
 Tools enable AI models to perform calculations, access external APIs, query databases, and manipulate files:
 
@@ -381,7 +381,7 @@ The second arguments is a `McpSchema.ReadResourceRequest`.
 
 ### Prompt Specification
 
-As part of the [Prompting capabilities](https://spec.modelcontextprotocol.io/specification/2024-11-05/server/prompts/), MCP provides a standardized way for servers to expose prompt templates to clients. 
+As part of the [Prompting capabilities](/specification/2024-11-05/server/prompts/), MCP provides a standardized way for servers to expose prompt templates to clients. 
 The Prompt Specification is a structured template for AI model interactions that enables consistent message formatting, parameter substitution, context injection, response formatting, and instruction templating.
 
 <Tabs>
@@ -422,7 +422,7 @@ The first argument is `McpAsyncServerExchange` for client interaction, and the s
 
 ### Using Sampling from a Server
 
-To use [Sampling capabilities](https://spec.modelcontextprotocol.io/specification/2024-11-05/client/sampling/), connect to a client that supports sampling. 
+To use [Sampling capabilities](/specification/2024-11-05/client/sampling/), connect to a client that supports sampling. 
 No special server configuration is needed, but verify client sampling support before making requests.
 Learn about [client sampling support](./mcp-client#sampling-support).