Fix broken documentation links (#2952)

docs/getting-started/welcome.mdx

@@ -5,14 +5,14 @@ description: The fast, Pythonic way to build MCP servers and clients.
 icon: hand-wave
 ---
 <img
-  src="/assets/brand/f-watercolor-waves.png"
+  src="/assets/brand/f-watercolor-waves-2.png"
 
   alt="'F' logo on a watercolor background"
   noZoom
   className="rounded-2xl block dark:hidden"
   />
 <img
-  src="/assets/brand/f-watercolor-waves-dark.png"
+  src="/assets/brand/f-watercolor-waves-dark-2.jpeg"
   alt="'F' logo on a watercolor background"
   noZoom
   className="rounded-2xl hidden dark:block"

docs/servers/prompts.mdx

@@ -418,7 +418,7 @@ mcp.enable(keys={"prompt:example_prompt"})   # Sends prompts/list_changed notifi
 
 Notifications are only sent when these operations occur within an active MCP request context (e.g., when called from within a tool or other MCP operation). Operations performed during server initialization do not trigger notifications.
 
-Clients can handle these notifications using a [message handler](/clients/messages) to automatically refresh their prompt lists or update their interfaces.
+Clients can handle these notifications using a [message handler](/clients/notifications) to automatically refresh their prompt lists or update their interfaces.
 
 ## Server Behavior
 

docs/servers/providers/transforms.mdx

@@ -28,7 +28,7 @@ FastMCP provides several transforms for common use cases:
 
 - **[Namespace](/servers/providers/namespace)** - Prefix component names to prevent conflicts when composing servers
 - **[Tool Transformation](/servers/providers/tool-transformation)** - Rename tools, modify descriptions, reshape arguments
-- **[Enabled](/servers/enabled)** - Control which components are visible at runtime
+- **[Enabled](/servers/visibility)** - Control which components are visible at runtime
 - **[Resources as Tools](/servers/providers/resources-as-tools)** - Expose resources to tool-only clients
 - **[Prompts as Tools](/servers/providers/prompts-as-tools)** - Expose prompts to tool-only clients
 

docs/servers/resources.mdx

@@ -401,7 +401,7 @@ mcp.enable(keys={"resource:data://example"})         # Sends resources/list_chan
 
 Notifications are only sent when these operations occur within an active MCP request context (e.g., when called from within a tool or other MCP operation). Operations performed during server initialization do not trigger notifications.
 
-Clients can handle these notifications using a [message handler](/clients/messages) to automatically refresh their resource lists or update their interfaces.
+Clients can handle these notifications using a [message handler](/clients/notifications) to automatically refresh their resource lists or update their interfaces.
 
 ### Annotations
 

docs/servers/tools.mdx

@@ -974,7 +974,7 @@ mcp.remove_tool("example_tool")         # Sends tools/list_changed notification
 
 Notifications are only sent when these operations occur within an active MCP request context (e.g., when called from within a tool or other MCP operation). Operations performed during server initialization do not trigger notifications.
 
-Clients can handle these notifications using a [message handler](/clients/messages) to automatically refresh their tool lists or update their interfaces.
+Clients can handle these notifications using a [message handler](/clients/notifications) to automatically refresh their tool lists or update their interfaces.
 
 ## Accessing the MCP Context
 

docs/v2/changelog.mdx

@@ -1161,10 +1161,10 @@ FastMCP 2.8.0 introduces powerful new ways to customize and control your MCP ser
 
 ### Tool Transformation
 
-The highlight of this release is first-class [**Tool Transformation**](/patterns/tool-transformation), a new feature that lets you create enhanced variations of existing tools. You can now easily rename arguments, hide parameters, modify descriptions, and even wrap tools with custom validation or post-processing logic—all without rewriting the original code. This makes it easier than ever to adapt generic tools for specific LLM use cases or to simplify complex APIs. Huge thanks to [@strawgate](https://github.com/strawgate) for partnering on this, starting with [#591](https://github.com/jlowin/fastmcp/discussions/591) and [#599](https://github.com/jlowin/fastmcp/pull/599) and continuing offline.
+The highlight of this release is first-class [**Tool Transformation**](/v2/patterns/tool-transformation), a new feature that lets you create enhanced variations of existing tools. You can now easily rename arguments, hide parameters, modify descriptions, and even wrap tools with custom validation or post-processing logic—all without rewriting the original code. This makes it easier than ever to adapt generic tools for specific LLM use cases or to simplify complex APIs. Huge thanks to [@strawgate](https://github.com/strawgate) for partnering on this, starting with [#591](https://github.com/jlowin/fastmcp/discussions/591) and [#599](https://github.com/jlowin/fastmcp/pull/599) and continuing offline.
 
 ### Component Control
-This release also gives you more granular control over which components are exposed to clients. With new [**tag-based filtering**](/servers/server#tag-based-filtering), you can selectively enable or disable tools, resources, and prompts based on tags, perfect for managing different environments or user permissions. Complementing this, every component now supports being [programmatically enabled or disabled](/servers/tools#disabling-tools), offering dynamic control over your server's capabilities.
+This release also gives you more granular control over which components are exposed to clients. With new [**tag-based filtering**](/v2/servers/server#tag-based-filtering), you can selectively enable or disable tools, resources, and prompts based on tags, perfect for managing different environments or user permissions. Complementing this, every component now supports being [programmatically enabled or disabled](/v2/servers/tools#disabling-tools), offering dynamic control over your server's capabilities.
 
 ### Tools-by-Default
 Finally, to improve compatibility with a wider range of LLM clients, this release changes the default behavior for OpenAPI integration: all API endpoints are now converted to `Tools` by default. This is a **breaking change** but pragmatically necessitated by the fact that the majority of MCP clients available today are, sadly, only compatible with MCP tools. Therefore, this change significantly simplifies the out-of-the-box experience and ensures your entire API is immediately accessible to any tool-using agent.

docs/v2/clients/client.mdx

@@ -179,7 +179,7 @@ async with client:
     print(result.data)  # 15
 ```
 
-See [Tools](/clients/tools) for detailed documentation.
+See [Tools](/v2/clients/tools) for detailed documentation.
 
 ### Resources
 
@@ -195,7 +195,7 @@ async with client:
     print(content[0].text)
 ```
 
-See [Resources](/clients/resources) for detailed documentation.
+See [Resources](/v2/clients/resources) for detailed documentation.
 
 ### Prompts
 
@@ -211,7 +211,7 @@ async with client:
     print(messages.messages)
 ```
 
-See [Prompts](/clients/prompts) for detailed documentation.
+See [Prompts](/v2/clients/prompts) for detailed documentation.
 
 ### Server Connectivity
 
@@ -314,26 +314,26 @@ The `Client` constructor accepts several configuration options:
 
 ### Transport Configuration
 
-For detailed transport configuration (headers, authentication, environment variables), see the [Transports](/clients/transports) documentation.
+For detailed transport configuration (headers, authentication, environment variables), see the [Transports](/v2/clients/transports) documentation.
 
 ## Next Steps
 
 Explore the detailed documentation for each operation type:
 
 ### Core Operations
-- **[Tools](/clients/tools)** - Execute server-side functions and handle results
-- **[Resources](/clients/resources)** - Access static and templated resources  
-- **[Prompts](/clients/prompts)** - Work with message templates and argument serialization
+- **[Tools](/v2/clients/tools)** - Execute server-side functions and handle results
+- **[Resources](/v2/clients/resources)** - Access static and templated resources  
+- **[Prompts](/v2/clients/prompts)** - Work with message templates and argument serialization
 
 ### Advanced Features
-- **[Logging](/clients/logging)** - Handle server log messages
-- **[Progress](/clients/progress)** - Monitor long-running operations
-- **[Sampling](/clients/sampling)** - Respond to server LLM requests
-- **[Roots](/clients/roots)** - Provide local context to servers
+- **[Logging](/v2/clients/logging)** - Handle server log messages
+- **[Progress](/v2/clients/progress)** - Monitor long-running operations
+- **[Sampling](/v2/clients/sampling)** - Respond to server LLM requests
+- **[Roots](/v2/clients/roots)** - Provide local context to servers
 
 ### Connection Details
-- **[Transports](/clients/transports)** - Configure connection methods and parameters
-- **[Authentication](/clients/auth/oauth)** - Set up OAuth and bearer token authentication
+- **[Transports](/v2/clients/transports)** - Configure connection methods and parameters
+- **[Authentication](/v2/clients/auth/oauth)** - Set up OAuth and bearer token authentication
 
 <Tip>
 The FastMCP Client is designed as a foundational tool. Use it directly for deterministic operations, or build higher-level agentic systems on top of its reliable, type-safe interface.

docs/v2/clients/messages.mdx

@@ -122,8 +122,8 @@ client = Client("server.py", message_handler=ToolCacheHandler())
 
 While the message handler receives server-initiated requests, for most use cases you should use the dedicated callback parameters instead:
 
-- **Sampling requests**: Use [`sampling_handler`](/clients/sampling)
-- **Progress requests**: Use [`progress_handler`](/clients/progress)  
-- **Log requests**: Use [`log_handler`](/clients/logging)
+- **Sampling requests**: Use [`sampling_handler`](/v2/clients/sampling)
+- **Progress requests**: Use [`progress_handler`](/v2/clients/progress)  
+- **Log requests**: Use [`log_handler`](/v2/clients/logging)
 
 The message handler is primarily for monitoring and handling notifications rather than responding to requests.

docs/v2/clients/sampling.mdx

@@ -160,7 +160,7 @@ client = Client(
 ```
 
 <Note>
-If the client doesn't provide a sampling handler, servers can optionally configure a fallback handler. See [Server Sampling](/servers/sampling#sampling-fallback-handler) for details.
+If the client doesn't provide a sampling handler, servers can optionally configure a fallback handler. See [Server Sampling](/v2/servers/sampling#sampling-fallback-handler) for details.
 </Note>
 
 ## Sampling Capabilities

docs/v2/clients/tasks.mdx

@@ -12,7 +12,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 The [MCP task protocol](https://modelcontextprotocol.io/specification/2025-11-25/basic/utilities/tasks) lets you request operations to run asynchronously. This returns a Task object immediately, letting you track progress, cancel operations, or await results.
 
-See [Server Background Tasks](/servers/tasks) for how to enable this on the server side.
+See [Server Background Tasks](/v2/servers/tasks) for how to enable this on the server side.
 
 ## Requesting Background Execution
 

docs/v2/clients/tools.mdx

@@ -125,7 +125,7 @@ async with client:
     )
 ```
 
-The structure and usage of `meta` is determined by your application. See [Client Metadata](/servers/context#client-metadata) in the server documentation to learn how to access this data in your tool implementations.
+The structure and usage of `meta` is determined by your application. See [Client Metadata](/v2/servers/context#client-metadata) in the server documentation to learn how to access this data in your tool implementations.
 
 ## Handling Results
 

docs/v2/community/showcase.mdx

@@ -62,4 +62,4 @@ We review submissions regularly and feature projects that provide value to the F
 
 ## Further Reading
 
-- [Contrib Modules](/patterns/contrib) - Community-contributed modules that are distributed with FastMCP itself
+- [Contrib Modules](/v2/patterns/contrib) - Community-contributed modules that are distributed with FastMCP itself

docs/v2/deployment/http.mdx

@@ -98,7 +98,7 @@ Now your server is accessible at `http://localhost:8000/api/mcp/`.
 Authentication is **highly recommended** for remote MCP servers. Some LLM clients require authentication for remote servers and will refuse to connect without it.
 </Warning>
 
-FastMCP supports multiple authentication methods to secure your remote server. See the [Authentication Overview](/servers/auth/authentication) for complete configuration options including Bearer tokens, JWT, and OAuth.
+FastMCP supports multiple authentication methods to secure your remote server. See the [Authentication Overview](/v2/servers/auth/authentication) for complete configuration options including Bearer tokens, JWT, and OAuth.
 
 If you're mounting an authenticated server under a path prefix, see [Mounting Authenticated Servers](#mounting-authenticated-servers) below for important routing considerations.
 
@@ -337,7 +337,7 @@ In this setup, the MCP server is accessible at the `/outer/inner/mcp/` path.
 
 ### FastAPI Integration
 
-For FastAPI-specific integration patterns including both mounting MCP servers into FastAPI apps and generating MCP servers from FastAPI apps, see the [FastAPI Integration guide](/integrations/fastapi).
+For FastAPI-specific integration patterns including both mounting MCP servers into FastAPI apps and generating MCP servers from FastAPI apps, see the [FastAPI Integration guide](/v2/integrations/fastapi).
 
 Here's a quick example showing how to add MCP to an existing FastAPI application:
 
@@ -574,7 +574,7 @@ if __name__ == "__main__":
     uvicorn.run(app, host="0.0.0.0", port=8000)
 ```
 
-For more details on OAuth authentication, see the [Authentication guide](/servers/auth).
+For more details on OAuth authentication, see the [Authentication guide](/v2/servers/auth).
 
 ## Production Deployment
 
@@ -598,7 +598,7 @@ When deploying FastMCP behind a load balancer or running multiple server instanc
 
 #### Understanding Sessions
 
-By default, FastMCP's Streamable HTTP transport maintains server-side sessions. Sessions enable stateful MCP features like [elicitation](/servers/elicitation) and [sampling](/servers/sampling), where the server needs to maintain context across multiple requests from the same client.
+By default, FastMCP's Streamable HTTP transport maintains server-side sessions. Sessions enable stateful MCP features like [elicitation](/v2/servers/elicitation) and [sampling](/v2/servers/sampling), where the server needs to maintain context across multiple requests from the same client.
 
 This works perfectly for single-instance deployments. However, sessions are stored in memory on each server instance, which creates challenges when scaling horizontally.
 
@@ -677,7 +677,7 @@ MCP_AUTH_TOKEN=secret uvicorn app:app --host 0.0.0.0 --port 8000
 
 <VersionBadge version="2.13.0" />
 
-If you're using the [OAuth Proxy](/servers/auth/oauth-proxy), FastMCP issues its own JWT tokens to clients instead of forwarding upstream provider tokens. This maintains proper OAuth 2.0 token boundaries.
+If you're using the [OAuth Proxy](/v2/servers/auth/oauth-proxy), FastMCP issues its own JWT tokens to clients instead of forwarding upstream provider tokens. This maintains proper OAuth 2.0 token boundaries.
 
 **Default Behavior (Development Only):**
 
@@ -717,11 +717,11 @@ auth = GitHubProvider(
 
 Both parameters are required for production. Without an explicit signing key, keys are signed using a key derived from the client_secret, which will cause invalidation upon rotation of the client secret. Without persistent storage, tokens are local to the server and won't be trusted across hosts. **Wrap your storage backend in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without encryption, tokens are stored in plaintext.
 
-For more details on the token architecture and key management, see [OAuth Proxy Key and Storage Management](/servers/auth/oauth-proxy#key-and-storage-management).
+For more details on the token architecture and key management, see [OAuth Proxy Key and Storage Management](/v2/servers/auth/oauth-proxy#key-and-storage-management).
 
 ## Testing Your Deployment
 
-Once your server is deployed, you'll need to verify it's accessible and functioning correctly. For comprehensive testing strategies including connectivity tests, client testing, and authentication testing, see the [Testing Your Server](/development/tests) guide.
+Once your server is deployed, you'll need to verify it's accessible and functioning correctly. For comprehensive testing strategies including connectivity tests, client testing, and authentication testing, see the [Testing Your Server](/v2/development/tests) guide.
 
 ## Hosting Your Server
 
@@ -733,4 +733,4 @@ This guide has shown you how to create an HTTP-accessible MCP server, but you'll
 - **Edge platforms** (Cloudflare Workers)
 - **Kubernetes clusters** (self-managed or managed)
 
-The key requirements are Python 3.10+ support and the ability to expose an HTTP port. Most providers will require you to package your server (requirements.txt, Dockerfile, etc.) according to their deployment format. For managed, zero-configuration deployment, see [FastMCP Cloud](/deployment/fastmcp-cloud).
+The key requirements are Python 3.10+ support and the ability to expose an HTTP port. Most providers will require you to package your server (requirements.txt, Dockerfile, etc.) according to their deployment format. For managed, zero-configuration deployment, see [FastMCP Cloud](/v2/deployment/fastmcp-cloud).

docs/v2/deployment/running-server.mdx

@@ -5,7 +5,7 @@ description: Learn how to run your FastMCP server locally for development and te
 icon: circle-play
 ---
 
-FastMCP servers can be run in different ways depending on your needs. This guide focuses on running servers locally for development and testing. For production deployment to a URL, see the [HTTP Deployment](/deployment/http) guide.
+FastMCP servers can be run in different ways depending on your needs. This guide focuses on running servers locally for development and testing. For production deployment to a URL, see the [HTTP Deployment](/v2/deployment/http) guide.
 
 ## The `run()` Method
 
@@ -89,7 +89,7 @@ Your server is now accessible at `http://localhost:8000/mcp`. This URL is the MC
 - Integration with web infrastructure
 - Remote deployment capabilities
 
-For production HTTP deployment with authentication and advanced configuration, see the [HTTP Deployment](/deployment/http) guide.
+For production HTTP deployment with authentication and advanced configuration, see the [HTTP Deployment](/v2/deployment/http) guide.
 
 ### SSE Transport (Legacy)
 
@@ -155,7 +155,7 @@ fastmcp run database_server.py -- --database-path /tmp/db.sqlite --debug
 
 This is useful for servers that need configuration files, database paths, API keys, or other runtime options.
 
-For more CLI features including development mode with the MCP Inspector, see the [CLI documentation](/patterns/cli).
+For more CLI features including development mode with the MCP Inspector, see the [CLI documentation](/v2/patterns/cli).
 
 ### Async Usage
 
@@ -212,7 +212,7 @@ if __name__ == "__main__":
     mcp.run(transport="http")  # Health check at http://localhost:8000/health
 ```
 
-Custom routes are served by the same web server as your MCP endpoint. They're available at the root of your domain while the MCP endpoint is at `/mcp/`. For more complex web applications, consider [mounting your MCP server into a FastAPI or Starlette app](/deployment/http#integration-with-web-frameworks).
+Custom routes are served by the same web server as your MCP endpoint. They're available at the root of your domain while the MCP endpoint is at `/mcp/`. For more complex web applications, consider [mounting your MCP server into a FastAPI or Starlette app](/v2/deployment/http#integration-with-web-frameworks).
 
 ## Alternative Initialization Patterns
 
@@ -255,4 +255,4 @@ def create_app():
 app = create_app()  # Uvicorn will use this
 ```
 
-See the [HTTP Deployment](/deployment/http) guide for more ASGI deployment patterns.
+See the [HTTP Deployment](/v2/deployment/http) guide for more ASGI deployment patterns.

docs/v2/development/contributing.mdx

@@ -126,7 +126,7 @@ uv run pytest tests/server/ -v
 uv run pytest
 ```
 
-Every new feature needs tests. See the [Testing Guide](/development/tests) for patterns and requirements.
+Every new feature needs tests. See the [Testing Guide](/v2/development/tests) for patterns and requirements.
 
 ### Documentation
 
@@ -178,7 +178,7 @@ Focus on the "why" - the code shows the "what". Keep it concise but complete.
 
 **Test Coverage**: Not every line needs testing, but every behavior does. Tests document intent and protect against regressions.
 
-**Breaking Changes**: May be acceptable in minor versions but must be clearly documented. See the [versioning policy](/development/releases#versioning-policy).
+**Breaking Changes**: May be acceptable in minor versions but must be clearly documented. See the [versioning policy](/v2/development/releases#versioning-policy).
 
 ## Special Modules
 

docs/v2/development/upgrade-guide.mdx

@@ -148,6 +148,6 @@ auth = GitHubProvider(
 ```
 
 **More information:**
-- [OAuth Token Security](/deployment/http#oauth-token-security) - Complete production setup guide
-- [Key and Storage Management](/servers/auth/oauth-proxy#key-and-storage-management) - Detailed explanation of defaults and production requirements
-- [OAuth Proxy Parameters](/servers/auth/oauth-proxy#configuration-parameters) - Parameter documentation
+- [OAuth Token Security](/v2/deployment/http#oauth-token-security) - Complete production setup guide
+- [Key and Storage Management](/v2/servers/auth/oauth-proxy#key-and-storage-management) - Detailed explanation of defaults and production requirements
+- [OAuth Proxy Parameters](/v2/servers/auth/oauth-proxy#configuration-parameters) - Parameter documentation

docs/v2/getting-started/installation.mdx

@@ -89,11 +89,11 @@ fastmcp==2.11.0  # Good
 fastmcp>=2.11.0  # Bad - will install breaking changes
 ```
 
-See the full [versioning and release policy](/development/releases#versioning-policy) for details on our public API, deprecation practices, and breaking change philosophy. 
+See the full [versioning and release policy](/v2/development/releases#versioning-policy) for details on our public API, deprecation practices, and breaking change philosophy. 
 
 ## Contributing to FastMCP
 
-Interested in contributing to FastMCP? See the [Contributing Guide](/development/contributing) for details on:
+Interested in contributing to FastMCP? See the [Contributing Guide](/v2/development/contributing) for details on:
 - Setting up your development environment
 - Running tests and pre-commit hooks
 - Submitting issues and pull requests

docs/v2/getting-started/quickstart.mdx

@@ -5,7 +5,7 @@ icon: rocket-launch
 
 Welcome! This guide will help you quickly set up FastMCP, run your first MCP server, and deploy a server to FastMCP Cloud.
 
-If you haven't already installed FastMCP, follow the [installation instructions](/getting-started/installation).
+If you haven't already installed FastMCP, follow the [installation instructions](/v2/getting-started/installation).
 
 ## Create a FastMCP Server
 
@@ -133,4 +133,4 @@ To deploy your server, you'll need a [GitHub account](https://github.com). Once
 
 That's it! FastMCP Cloud will build and deploy your server, making it available at a URL like `https://your-project.fastmcp.app/mcp`. You can chat with it to test its functionality, or connect to it from any LLM client that supports the MCP protocol.
 
-For more details, see the [FastMCP Cloud guide](/deployment/fastmcp-cloud).
+For more details, see the [FastMCP Cloud guide](/v2/deployment/fastmcp-cloud).

docs/v2/getting-started/welcome.mdx

@@ -42,7 +42,7 @@ FastMCP pioneered Python MCP development, and FastMCP 1.0 was incorporated into
 
 **This is FastMCP 2.0,** the actively maintained version that extends far beyond basic protocol implementation. While the SDK provides core functionality, FastMCP 2.0 delivers everything needed for production: advanced MCP patterns (server composition, proxying, OpenAPI/FastAPI generation, tool transformation), enterprise auth (Google, GitHub, Azure, Auth0, WorkOS, and more), deployment tools, testing frameworks, and comprehensive client libraries.
 
-Ready to build? Start with our [installation guide](/getting-started/installation) or jump straight to the [quickstart](/getting-started/quickstart).
+Ready to build? Start with our [installation guide](/v2/getting-started/installation) or jump straight to the [quickstart](/v2/getting-started/quickstart).
 
 FastMCP is made with 💙 by [Prefect](https://www.prefect.io/).
 

docs/v2/integrations/anthropic.mdx

@@ -120,7 +120,7 @@ The MCP connector supports OAuth authentication through authorization tokens, wh
 
 The simplest way to add authentication to the server is to use a bearer token scheme. 
 
-For this example, we'll quickly generate our own tokens with FastMCP's `RSAKeyPair` utility, but this may not be appropriate for production use. For more details, see the complete server-side [Token Verification](/servers/auth/token-verification) documentation. 
+For this example, we'll quickly generate our own tokens with FastMCP's `RSAKeyPair` utility, but this may not be appropriate for production use. For more details, see the complete server-side [Token Verification](/v2/servers/auth/token-verification) documentation. 
 
 We'll start by creating an RSA key pair to sign and verify tokens.
 

docs/v2/integrations/auth0.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.12.4" />
 
-This guide shows you how to secure your FastMCP server using **Auth0 OAuth**. While Auth0 does have support for Dynamic Client Registration, it is not enabled by default so this integration uses the [**OIDC Proxy**](/servers/auth/oidc-proxy) pattern to bridge Auth0's dynamic OIDC configuration with MCP's authentication requirements.
+This guide shows you how to secure your FastMCP server using **Auth0 OAuth**. While Auth0 does have support for Dynamic Client Registration, it is not enabled by default so this integration uses the [**OIDC Proxy**](/v2/servers/auth/oidc-proxy) pattern to bridge Auth0's dynamic OIDC configuration with MCP's authentication requirements.
 
 ## Configuration
 
@@ -188,7 +188,7 @@ mcp = FastMCP(name="Production Auth0 App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 <Info>
@@ -235,7 +235,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_AUTH0_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_AUTH0_REDIRECT_PATH" default="/auth/callback">

docs/v2/integrations/authkit.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.11.0" />
 
-This guide shows you how to secure your FastMCP server using WorkOS's **AuthKit**, a complete authentication and user management solution. This integration uses the [**Remote OAuth**](/servers/auth/remote-oauth) pattern, where AuthKit handles user login and your FastMCP server validates the tokens.
+This guide shows you how to secure your FastMCP server using WorkOS's **AuthKit**, a complete authentication and user management solution. This integration uses the [**Remote OAuth**](/v2/servers/auth/remote-oauth) pattern, where AuthKit handles user login and your FastMCP server validates the tokens.
 
 
 ## Configuration

docs/v2/integrations/aws-cognito.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.12.4" />
 
-This guide shows you how to secure your FastMCP server using **AWS Cognito user pools**. Since AWS Cognito doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/servers/auth/oauth-proxy) pattern to bridge AWS Cognito's traditional OAuth with MCP's authentication requirements. It also includes robust JWT token validation, ensuring enterprise-grade authentication.
+This guide shows you how to secure your FastMCP server using **AWS Cognito user pools**. Since AWS Cognito doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/v2/servers/auth/oauth-proxy) pattern to bridge AWS Cognito's traditional OAuth with MCP's authentication requirements. It also includes robust JWT token validation, ensuring enterprise-grade authentication.
 
 ## Configuration
 
@@ -235,7 +235,7 @@ mcp = FastMCP(name="Production AWS Cognito App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 ## Environment Variables
@@ -278,7 +278,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_AWS_COGNITO_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_AWS_COGNITO_REDIRECT_PATH" default="/auth/callback">

docs/v2/integrations/azure.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.13.0" />
 
-This guide shows you how to secure your FastMCP server using **Azure OAuth** (Microsoft Entra ID). Since Azure doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/servers/auth/oauth-proxy) pattern to bridge Azure's traditional OAuth with MCP's authentication requirements. FastMCP validates Azure JWTs against your application's client_id.
+This guide shows you how to secure your FastMCP server using **Azure OAuth** (Microsoft Entra ID). Since Azure doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/v2/servers/auth/oauth-proxy) pattern to bridge Azure's traditional OAuth with MCP's authentication requirements. FastMCP validates Azure JWTs against your application's client_id.
 
 ## Configuration
 
@@ -277,7 +277,7 @@ mcp = FastMCP(name="Production Azure App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 ## Environment Variables
@@ -322,7 +322,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_AZURE_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_AZURE_REDIRECT_PATH" default="/auth/callback">

docs/v2/integrations/claude-desktop.mdx

@@ -277,7 +277,7 @@ if __name__ == "__main__":
 
 ### Authentication
 
-For authenticated remote servers, create an authenticated client following the guidance in the [client auth documentation](/clients/auth/bearer) and pass it to the proxy:
+For authenticated remote servers, create an authenticated client following the guidance in the [client auth documentation](/v2/clients/auth/bearer) and pass it to the proxy:
 
 ```python auth_proxy_server.py {7}
 from fastmcp import FastMCP, Client

docs/v2/integrations/descope.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx";
 
 <VersionBadge version="2.12.4" />
 
-This guide shows you how to secure your FastMCP server using [**Descope**](https://www.descope.com), a complete authentication and user management solution. This integration uses the [**Remote OAuth**](/servers/auth/remote-oauth) pattern, where Descope handles user login and your FastMCP server validates the tokens.
+This guide shows you how to secure your FastMCP server using [**Descope**](https://www.descope.com), a complete authentication and user management solution. This integration uses the [**Remote OAuth**](/v2/servers/auth/remote-oauth) pattern, where Descope handles user login and your FastMCP server validates the tokens.
 
 ## Configuration
 

docs/v2/integrations/discord.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.13.2" />
 
-This guide shows you how to secure your FastMCP server using **Discord OAuth**. Since Discord doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/servers/auth/oauth-proxy) pattern to bridge Discord's traditional OAuth with MCP's authentication requirements.
+This guide shows you how to secure your FastMCP server using **Discord OAuth**. Since Discord doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/v2/servers/auth/oauth-proxy) pattern to bridge Discord's traditional OAuth with MCP's authentication requirements.
 
 ## Configuration
 
@@ -180,7 +180,7 @@ mcp = FastMCP(name="Production Discord App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 ## Environment Variables
@@ -215,7 +215,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_DISCORD_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_DISCORD_REDIRECT_PATH" default="/auth/callback">

docs/v2/integrations/fastapi.mdx

@@ -211,7 +211,7 @@ if __name__ == "__main__":
 
 ### Custom Route Mapping
 
-Because FastMCP's FastAPI integration is based on its [OpenAPI integration](/integrations/openapi), you can customize how endpoints are converted to MCP components in exactly the same way. For example, here we use a `RouteMap` to map all GET requests to MCP resources, and all POST/PUT/DELETE requests to MCP tools:
+Because FastMCP's FastAPI integration is based on its [OpenAPI integration](/v2/integrations/openapi), you can customize how endpoints are converted to MCP components in exactly the same way. For example, here we use a `RouteMap` to map all GET requests to MCP resources, and all POST/PUT/DELETE requests to MCP tools:
 
 ```python
 # Assumes the FastAPI app from above is already defined
@@ -245,7 +245,7 @@ mcp = FastMCP.from_fastapi(
 ```
 
 <Tip>
-To learn more about customizing the conversion process, see the [OpenAPI Integration guide](/integrations/openapi).
+To learn more about customizing the conversion process, see the [OpenAPI Integration guide](/v2/integrations/openapi).
 </Tip>
 
 ### Authentication and Headers
@@ -396,7 +396,7 @@ app = FastAPI()
 app.mount("/mcp", mcp.http_app())  # Session manager won't initialize
 ```
 
-If you're mounting an authenticated MCP server under a path prefix, see [Mounting Authenticated Servers](/deployment/http#mounting-authenticated-servers) for important OAuth routing considerations.
+If you're mounting an authenticated MCP server under a path prefix, see [Mounting Authenticated Servers](/v2/deployment/http#mounting-authenticated-servers) for important OAuth routing considerations.
 
 ### CORS Middleware
 
@@ -448,4 +448,4 @@ This pattern ensures both your app's initialization logic and the MCP server's s
 2. **Design purpose-built MCP tools** - Better than auto-converting complex APIs
 3. **Keep tool parameters simple** - LLMs perform better with focused interfaces
 
-For more details on configuration options, see the [OpenAPI Integration guide](/integrations/openapi).
+For more details on configuration options, see the [OpenAPI Integration guide](/v2/integrations/openapi).

docs/v2/integrations/gemini.mdx

@@ -89,7 +89,7 @@ Okay, I rolled 3 dice and got a 5, 4, and 1.
 
 ### Remote & Authenticated Servers
 
-In the above example, we connected to our local server using `stdio` transport. Because we're using a FastMCP client, you can also connect to any local or remote MCP server, using any [transport](/clients/transports) or [auth](/clients/auth) method supported by FastMCP, simply by changing the client configuration.
+In the above example, we connected to our local server using `stdio` transport. Because we're using a FastMCP client, you can also connect to any local or remote MCP server, using any [transport](/v2/clients/transports) or [auth](/v2/clients/auth) method supported by FastMCP, simply by changing the client configuration.
 
 For example, to connect to a remote, authenticated server, you can use the following client:
 

docs/v2/integrations/github.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.12.0" />
 
-This guide shows you how to secure your FastMCP server using **GitHub OAuth**. Since GitHub doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/servers/auth/oauth-proxy) pattern to bridge GitHub's traditional OAuth with MCP's authentication requirements.
+This guide shows you how to secure your FastMCP server using **GitHub OAuth**. Since GitHub doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/v2/servers/auth/oauth-proxy) pattern to bridge GitHub's traditional OAuth with MCP's authentication requirements.
 
 ## Configuration
 
@@ -172,7 +172,7 @@ mcp = FastMCP(name="Production GitHub App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 ## Environment Variables
@@ -209,7 +209,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_GITHUB_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_GITHUB_REDIRECT_PATH" default="/auth/callback">

docs/v2/integrations/google.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.12.0" />
 
-This guide shows you how to secure your FastMCP server using **Google OAuth**. Since Google doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/servers/auth/oauth-proxy) pattern to bridge Google's traditional OAuth with MCP's authentication requirements.
+This guide shows you how to secure your FastMCP server using **Google OAuth**. Since Google doesn't support Dynamic Client Registration, this integration uses the [**OAuth Proxy**](/v2/servers/auth/oauth-proxy) pattern to bridge Google's traditional OAuth with MCP's authentication requirements.
 
 ## Configuration
 
@@ -186,7 +186,7 @@ mcp = FastMCP(name="Production Google App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 ## Environment Variables
@@ -223,7 +223,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_GOOGLE_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_GOOGLE_REDIRECT_PATH" default="/auth/callback">

docs/v2/integrations/mcp-json-configuration.mdx

@@ -78,7 +78,7 @@ This format is widely adopted across the MCP ecosystem:
 ## Overview
 
 <Note>
-**For the best experience, use FastMCP's first-class integrations:** [`fastmcp install claude-code`](/integrations/claude-code), [`fastmcp install claude-desktop`](/integrations/claude-desktop), or [`fastmcp install cursor`](/integrations/cursor). Use MCP JSON generation for advanced use cases and unsupported clients.
+**For the best experience, use FastMCP's first-class integrations:** [`fastmcp install claude-code`](/v2/integrations/claude-code), [`fastmcp install claude-desktop`](/v2/integrations/claude-desktop), or [`fastmcp install cursor`](/v2/integrations/cursor). Use MCP JSON generation for advanced use cases and unsupported clients.
 </Note>
 
 The `fastmcp install mcp-json` command generates configuration in the standard `mcpServers` format used across the MCP ecosystem. This is useful when:
@@ -363,13 +363,13 @@ The generated configuration works with any MCP-compatible application:
 
 ### Claude Desktop
 <Note>
-**Prefer [`fastmcp install claude-desktop`](/integrations/claude-desktop)** for automatic installation. Use MCP JSON for advanced configuration needs.
+**Prefer [`fastmcp install claude-desktop`](/v2/integrations/claude-desktop)** for automatic installation. Use MCP JSON for advanced configuration needs.
 </Note>
 Copy the `mcpServers` object into `~/.claude/claude_desktop_config.json`
 
 ### Cursor
 <Note>
-**Prefer [`fastmcp install cursor`](/integrations/cursor)** for automatic installation. Use MCP JSON for advanced configuration needs.
+**Prefer [`fastmcp install cursor`](/v2/integrations/cursor)** for automatic installation. Use MCP JSON for advanced configuration needs.
 </Note>
 Add to `~/.cursor/mcp.json`
 

docs/v2/integrations/oci.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.13.0" />
 
-This guide shows you how to secure your FastMCP server using **OCI IAM OAuth**. Since OCI IAM doesn't support Dynamic Client Registration, this integration uses the [**OIDC Proxy**](/servers/auth/oidc-proxy) pattern to bridge OCI's traditional OAuth with MCP's authentication requirements.
+This guide shows you how to secure your FastMCP server using **OCI IAM OAuth**. Since OCI IAM doesn't support Dynamic Client Registration, this integration uses the [**OIDC Proxy**](/v2/servers/auth/oidc-proxy) pattern to bridge OCI's traditional OAuth with MCP's authentication requirements.
 
 ## Configuration
 
@@ -248,7 +248,7 @@ mcp = FastMCP(name="Production OCI App", auth=auth_provider)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at Rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 <Info>

docs/v2/integrations/openai.mdx

@@ -117,7 +117,7 @@ The Responses API can include headers to authenticate the request, which means y
 
 The simplest way to add authentication to the server is to use a bearer token scheme. 
 
-For this example, we'll quickly generate our own tokens with FastMCP's `RSAKeyPair` utility, but this may not be appropriate for production use. For more details, see the complete server-side [Token Verification](/servers/auth/token-verification) documentation. 
+For this example, we'll quickly generate our own tokens with FastMCP's `RSAKeyPair` utility, but this may not be appropriate for production use. For more details, see the complete server-side [Token Verification](/v2/servers/auth/token-verification) documentation. 
 
 We'll start by creating an RSA key pair to sign and verify tokens.
 

docs/v2/integrations/scalekit.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.13.0" />
 
-Install auth stack to your FastMCP server with [Scalekit](https://scalekit.com) using the [Remote OAuth](/servers/auth/remote-oauth) pattern: Scalekit handles user authentication, and the MCP server validates issued tokens.
+Install auth stack to your FastMCP server with [Scalekit](https://scalekit.com) using the [Remote OAuth](/v2/servers/auth/remote-oauth) pattern: Scalekit handles user authentication, and the MCP server validates issued tokens.
 
 ### Prerequisites
 

docs/v2/integrations/supabase.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 
 <VersionBadge version="2.13.0" />
 
-This guide shows you how to secure your FastMCP server using **Supabase Auth**. This integration uses the [**Remote OAuth**](/servers/auth/remote-oauth) pattern, where Supabase handles user authentication and your FastMCP server validates the tokens.
+This guide shows you how to secure your FastMCP server using **Supabase Auth**. This integration uses the [**Remote OAuth**](/v2/servers/auth/remote-oauth) pattern, where Supabase handles user authentication and your FastMCP server validates the tokens.
 
 ## Configuration
 

docs/v2/integrations/workos.mdx

@@ -13,7 +13,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 Secure your FastMCP server with WorkOS Connect authentication. This integration uses the OAuth Proxy pattern to handle authentication through WorkOS Connect while maintaining compatibility with MCP clients.
 
 <Note>
-This guide covers WorkOS Connect applications. For Dynamic Client Registration (DCR) with AuthKit, see the [AuthKit integration](/integrations/authkit) instead.
+This guide covers WorkOS Connect applications. For Dynamic Client Registration (DCR) with AuthKit, see the [AuthKit integration](/v2/integrations/authkit) instead.
 </Note>
 
 ## Configuration
@@ -165,7 +165,7 @@ mcp = FastMCP(name="Production WorkOS App", auth=auth)
 <Note>
 Parameters (`jwt_signing_key` and `client_storage`) work together to ensure tokens and client registrations survive server restarts. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.
 
-For complete details on these parameters, see the [OAuth Proxy documentation](/servers/auth/oauth-proxy#configuration-parameters).
+For complete details on these parameters, see the [OAuth Proxy documentation](/v2/servers/auth/oauth-proxy#configuration-parameters).
 </Note>
 
 ## Environment Variables
@@ -206,7 +206,7 @@ Public URL where OAuth endpoints will be accessible (includes any mount path)
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_WORKOS_ISSUER_URL" default="Uses BASE_URL">
-Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for details.
+Issuer URL for OAuth metadata (defaults to `BASE_URL`). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for details.
 </ParamField>
 
 <ParamField path="FASTMCP_SERVER_AUTH_WORKOS_REDIRECT_PATH" default="/auth/callback">

docs/v2/patterns/cli.mdx

@@ -192,7 +192,7 @@ The `--skip-env` flag is useful when:
 - You want to test the server without environment setup
 </Note>
 
-See [Server Configuration](/deployment/server-configuration) for detailed documentation on fastmcp.json.
+See [Server Configuration](/v2/deployment/server-configuration) for detailed documentation on fastmcp.json.
 
 #### MCP Configuration
 

docs/v2/patterns/tool-transformation.mdx

@@ -522,7 +522,7 @@ directly in the MCPConfig json file.
 The `tools` section is a dictionary of tool names to tool configurations. Each tool configuration is a
 dictionary of tool properties.
 
-See the [MCPConfigTransport](/clients/transports#tool-transformation-with-fastmcp-and-mcpconfig) documentation for more details.
+See the [MCPConfigTransport](/v2/clients/transports#tool-transformation-with-fastmcp-and-mcpconfig) documentation for more details.
 
 
 ## Output Schema Control
@@ -698,7 +698,7 @@ This pattern provides several benefits:
 - **Scalable**: Easily add new tools by wrapping additional client methods
 
 ### Adapting Remote or Generated Tools
-This is one of the most common reasons to use tool transformation. Tools from remote MCP servers (via a [proxy](/servers/proxy)) or generated from an [OpenAPI spec](/integrations/openapi) are often too generic for direct use by an LLM. You can use transformation to create a simpler, more intuitive version for your specific needs.
+This is one of the most common reasons to use tool transformation. Tools from remote MCP servers (via a [proxy](/v2/servers/proxy)) or generated from an [OpenAPI spec](/v2/integrations/openapi) are often too generic for direct use by an LLM. You can use transformation to create a simpler, more intuitive version for your specific needs.
 
 ### Chaining Transformations
 You can chain transformations by using an already transformed tool as the parent for a new transformation. This lets you build up complex behaviors in layers, for example, first renaming arguments, and then adding validation logic to the renamed tool.

docs/v2/servers/auth/authentication.mdx

@@ -92,7 +92,7 @@ This example configures token validation against a JWT issuer. The `JWTVerifier`
 
 `TokenVerifier` works well when you control both the token issuer and your MCP server, or when integrating with existing JWT-based infrastructure.
 
-→ **Complete guide**: [Token Verification](/servers/auth/token-verification)
+→ **Complete guide**: [Token Verification](/v2/servers/auth/token-verification)
 
 ### RemoteAuthProvider
 
@@ -120,7 +120,7 @@ This example uses WorkOS AuthKit as the external identity provider. The `AuthKit
 
 `RemoteAuthProvider` is ideal for production applications when your identity provider supports Dynamic Client Registration (DCR). This enables fully automated authentication without manual client configuration.
 
-→ **Complete guide**: [Remote OAuth](/servers/auth/remote-oauth)
+→ **Complete guide**: [Remote OAuth](/v2/servers/auth/remote-oauth)
 
 ### OAuthProxy
 
@@ -151,7 +151,7 @@ This example uses the GitHub provider, which extends `OAuthProxy` with GitHub-sp
 
 `OAuthProxy` is essential when integrating with OAuth providers that don't support DCR. This includes most established providers like GitHub, Google, and Azure, which require manual app registration through their developer consoles.
 
-→ **Complete guide**: [OAuth Proxy](/servers/auth/oauth-proxy)
+→ **Complete guide**: [OAuth Proxy](/v2/servers/auth/oauth-proxy)
 
 ### OAuthProvider
 
@@ -176,7 +176,7 @@ This example shows the basic structure of a custom OAuth provider. The actual im
 
 `OAuthProvider` should be used only when you have specific requirements that external providers cannot meet and the expertise to implement OAuth securely.
 
-→ **Complete guide**: [Full OAuth Server](/servers/auth/full-oauth-server)
+→ **Complete guide**: [Full OAuth Server](/v2/servers/auth/full-oauth-server)
 
 ## Configuration Approaches
 

docs/v2/servers/auth/full-oauth-server.mdx

@@ -13,7 +13,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx"
 <Warning>
 **This is an extremely advanced pattern that most users should avoid.** Building a secure OAuth 2.1 server requires deep expertise in authentication protocols, cryptography, and security best practices. The complexity extends far beyond initial implementation to include ongoing security monitoring, threat response, and compliance maintenance.
 
-**Use [Remote OAuth](/servers/auth/remote-oauth) instead** unless you have compelling requirements that external identity providers cannot meet, such as air-gapped environments or specialized compliance needs.
+**Use [Remote OAuth](/v2/servers/auth/remote-oauth) instead** unless you have compelling requirements that external identity providers cannot meet, such as air-gapped environments or specialized compliance needs.
 </Warning>
 
 The Full OAuth Server pattern exists to support the MCP protocol specification's requirements. Your FastMCP server becomes both an Authorization Server and Resource Server, handling the complete authentication lifecycle from user login to token validation.

docs/v2/servers/auth/oauth-proxy.mdx

@@ -10,7 +10,7 @@ import { VersionBadge } from "/snippets/version-badge.mdx";
 
 <VersionBadge version="2.12.0" />
 
-The OAuth proxy enables FastMCP servers to authenticate with OAuth providers that **don't support Dynamic Client Registration (DCR)**. This includes virtually all traditional OAuth providers: GitHub, Google, Azure, AWS, Discord, Facebook, and most enterprise identity systems. For providers that do support DCR (like Descope and WorkOS AuthKit), use [`RemoteAuthProvider`](/servers/auth/remote-oauth) instead.
+The OAuth proxy enables FastMCP servers to authenticate with OAuth providers that **don't support Dynamic Client Registration (DCR)**. This includes virtually all traditional OAuth providers: GitHub, Google, Azure, AWS, Discord, Facebook, and most enterprise identity systems. For providers that do support DCR (like Descope and WorkOS AuthKit), use [`RemoteAuthProvider`](/v2/servers/auth/remote-oauth) instead.
 
 MCP clients expect to register automatically and obtain credentials on the fly, but traditional providers require manual app registration through their developer consoles. The OAuth proxy bridges this gap by presenting a DCR-compliant interface to MCP clients while using your pre-registered credentials with the upstream provider. When a client attempts to register, the proxy returns your fixed credentials. When a client initiates authorization, the proxy handles the complexity of callback forwarding—storing the client's dynamic callback URL, using its own fixed callback with the provider, then forwarding back to the client after token exchange.
 
@@ -19,7 +19,7 @@ This approach enables any MCP client (whether using random localhost ports or fi
 <Note>
   For providers that support OIDC discovery (Auth0, Google with OIDC
   configuration, Azure AD), consider using [`OIDC
-  Proxy`](/servers/auth/oidc-proxy) for automatic configuration. OIDC Proxy
+  Proxy`](/v2/servers/auth/oidc-proxy) for automatic configuration. OIDC Proxy
   extends the OAuth proxy to automatically discover endpoints from the provider's
   `/.well-known/openid-configuration` URL, simplifying setup.
 </Note>
@@ -105,7 +105,7 @@ mcp = FastMCP(name="My Server", auth=auth)
 </ParamField>
 
 <ParamField body="token_verifier" type="TokenVerifier" required>
-  A [`TokenVerifier`](/servers/auth/token-verification) instance to validate the
+  A [`TokenVerifier`](/v2/servers/auth/token-verification) instance to validate the
   provider's tokens
 </ParamField>
 
@@ -146,7 +146,7 @@ mcp = FastMCP(name="My Server", auth=auth)
   )
   ```
 
-  See the [HTTP Deployment guide](/deployment/http#mounting-authenticated-servers) for complete mounting examples.
+  See the [HTTP Deployment guide](/v2/deployment/http#mounting-authenticated-servers) for complete mounting examples.
 </ParamField>
 
 <ParamField body="service_documentation_url" type="AnyHttpUrl | str | None">
@@ -221,7 +221,7 @@ These parameters are included in all token requests to the upstream provider.
   **Default behavior:**
   By default, clients are automatically persisted to an encrypted disk store, allowing them to survive server restarts as long as the filesystem remains accessible. This means MCP clients only need to register once and can reconnect seamlessly. The disk store is encrypted using a key derived from the JWT Signing Key (which is derived from the upstream client secret by default). For client registrations to survive upstream client secret rotation, you should provide a JWT Signing Key or your own client_storage.
 
-For production deployments with multiple servers or cloud deployments, see [Storage Backends](/servers/storage-backends) for available options.
+For production deployments with multiple servers or cloud deployments, see [Storage Backends](/v2/servers/storage-backends) for available options.
 
 <Warning>
   **When providing custom storage**, wrap it in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest:
@@ -277,7 +277,7 @@ auth = OAuthProxy(..., client_storage=MemoryStore())
   )
   ```
 
-  See [HTTP Deployment - OAuth Token Security](/deployment/http#oauth-token-security) for complete production setup.
+  See [HTTP Deployment - OAuth Token Security](/v2/deployment/http#oauth-token-security) for complete production setup.
 </ParamField>
 
 
@@ -348,7 +348,7 @@ The OAuth proxy requires a compatible `TokenVerifier` to validate tokens from yo
 - **Opaque tokens with RFC 7662 introspection** (Auth0, Okta, WorkOS): Use `IntrospectionTokenVerifier`
 - **Opaque tokens (provider-specific)** (GitHub, Discord): Use provider-specific verifiers like `GitHubTokenVerifier`
 
-See the [Token Verification guide](/servers/auth/token-verification) for detailed setup instructions for your provider.
+See the [Token Verification guide](/v2/servers/auth/token-verification) for detailed setup instructions for your provider.
 
 ### Scope Configuration
 
@@ -536,7 +536,7 @@ The OAuth proxy requires cryptographic keys for JWT signing and storage encrypti
 - **Linux**: Keys are ephemeral (random salt at startup). Storage defaults to memory. Tokens become invalid on server restart.
 
 **For production:**
-Configure the following parameters together: provide a unique `jwt_signing_key` (for signing FastMCP JWTs), and a shared `client_storage` backend (for storing tokens). Both are required for production deployments. Use a network-accessible storage backend like Redis or DynamoDB rather than local disk storage. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** (see the `client_storage` parameter documentation above for examples). The keys accept any secret string and derive proper cryptographic keys using HKDF. See [OAuth Token Security](/deployment/http#oauth-token-security) and [Storage Backends](/servers/storage-backends) for complete production setup.
+Configure the following parameters together: provide a unique `jwt_signing_key` (for signing FastMCP JWTs), and a shared `client_storage` backend (for storing tokens). Both are required for production deployments. Use a network-accessible storage backend like Redis or DynamoDB rather than local disk storage. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** (see the `client_storage` parameter documentation above for examples). The keys accept any secret string and derive proper cryptographic keys using HKDF. See [OAuth Token Security](/v2/deployment/http#oauth-token-security) and [Storage Backends](/v2/servers/storage-backends) for complete production setup.
 
 ### Confused Deputy Attacks
 

docs/v2/servers/auth/oidc-proxy.mdx

@@ -10,9 +10,9 @@ import { VersionBadge } from "/snippets/version-badge.mdx";
 
 <VersionBadge version="2.12.4" />
 
-The OIDC proxy enables FastMCP servers to authenticate with OIDC providers that **don't support Dynamic Client Registration (DCR)** out of the box. This includes OAuth providers like: Auth0, Google, Azure, AWS, etc. For providers that do support DCR (like WorkOS AuthKit), use [`RemoteAuthProvider`](/servers/auth/remote-oauth) instead.
+The OIDC proxy enables FastMCP servers to authenticate with OIDC providers that **don't support Dynamic Client Registration (DCR)** out of the box. This includes OAuth providers like: Auth0, Google, Azure, AWS, etc. For providers that do support DCR (like WorkOS AuthKit), use [`RemoteAuthProvider`](/v2/servers/auth/remote-oauth) instead.
 
-The OIDC proxy is built upon [`OAuthProxy`](/servers/auth/oauth-proxy) so it has all the same functionality under the covers.
+The OIDC proxy is built upon [`OAuthProxy`](/v2/servers/auth/oauth-proxy) so it has all the same functionality under the covers.
 
 ## Implementation
 
@@ -161,7 +161,7 @@ Set this if your provider requires a specific authentication method and the defa
 
   By default on Mac/Windows, clients are automatically persisted to encrypted disk storage, allowing them to survive server restarts as long as the filesystem remains accessible. This means MCP clients only need to register once and can reconnect seamlessly. On Linux where keyring isn't available, ephemeral storage is used to match the ephemeral key strategy.
 
-For production deployments with multiple servers or cloud deployments, use a network-accessible storage backend rather than local disk storage. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest.** See [Storage Backends](/servers/storage-backends) for available options.
+For production deployments with multiple servers or cloud deployments, use a network-accessible storage backend rather than local disk storage. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest.** See [Storage Backends](/v2/servers/storage-backends) for available options.
 
 Testing with in-memory storage (unencrypted):
 
@@ -193,7 +193,7 @@ auth = OIDCProxy(
 </ParamField>
 
 <ParamField body="require_authorization_consent" type="bool" default="True">
-  Whether to require user consent before authorizing MCP clients. When enabled (default), users see a consent screen that displays which client is requesting access. See [OAuthProxy documentation](/servers/auth/oauth-proxy#confused-deputy-attacks) for details on confused deputy attack protection.
+  Whether to require user consent before authorizing MCP clients. When enabled (default), users see a consent screen that displays which client is requesting access. See [OAuthProxy documentation](/v2/servers/auth/oauth-proxy#confused-deputy-attacks) for details on confused deputy attack protection.
 </ParamField>
 
 <ParamField body="consent_csp_policy" type="str | None" default="None">

docs/v2/servers/auth/remote-oauth.mdx

@@ -30,9 +30,9 @@ RemoteAuthProvider works with identity providers that support **Dynamic Client R
 | **Credentials** | Dynamic per client | Fixed app credentials |
 | **Configuration** | Zero client config | Pre-shared credentials |
 | **Examples** | Descope, WorkOS AuthKit, modern OIDC | GitHub, Google, Azure |
-| **FastMCP Class** | `RemoteAuthProvider` | [`OAuthProxy`](/servers/auth/oauth-proxy) |
+| **FastMCP Class** | `RemoteAuthProvider` | [`OAuthProxy`](/v2/servers/auth/oauth-proxy) |
 
-If your provider doesn't support DCR (most traditional OAuth providers), you'll need to use [`OAuth Proxy`](/servers/auth/oauth-proxy) instead, which bridges the gap between MCP's DCR expectations and fixed OAuth credentials.
+If your provider doesn't support DCR (most traditional OAuth providers), you'll need to use [`OAuth Proxy`](/v2/servers/auth/oauth-proxy) instead, which bridges the gap between MCP's DCR expectations and fixed OAuth credentials.
 
 ## The Remote OAuth Challenge
 
@@ -84,7 +84,7 @@ FastMCP provides `RemoteAuthProvider` to handle the complexities of remote OAuth
 
 ### RemoteAuthProvider
 
-`RemoteAuthProvider` works by composing a [`TokenVerifier`](/servers/auth/token-verification) with authorization server information. A `TokenVerifier` is another FastMCP authentication class that focuses solely on token validation - signature verification, expiration checking, and claim extraction. The `RemoteAuthProvider` takes that token validation capability and adds the OAuth discovery endpoints that enable MCP clients to automatically find and authenticate with your identity provider.
+`RemoteAuthProvider` works by composing a [`TokenVerifier`](/v2/servers/auth/token-verification) with authorization server information. A `TokenVerifier` is another FastMCP authentication class that focuses solely on token validation - signature verification, expiration checking, and claim extraction. The `RemoteAuthProvider` takes that token validation capability and adds the OAuth discovery endpoints that enable MCP clients to automatically find and authenticate with your identity provider.
 
 This composition pattern means you can use any token validation strategy while maintaining consistent OAuth discovery behavior:
 - **JWT tokens**: Use `JWTVerifier` for self-contained tokens
@@ -197,7 +197,7 @@ The `AuthKitProvider` automatically configures JWT validation against WorkOS's p
 
 WorkOS's support for Dynamic Client Registration makes it particularly well-suited for MCP applications. Clients can automatically register themselves with your WorkOS project and obtain the credentials needed for authentication without manual intervention.
 
-→ **Complete WorkOS tutorial**: [AuthKit Integration Guide](/integrations/authkit)
+→ **Complete WorkOS tutorial**: [AuthKit Integration Guide](/v2/integrations/authkit)
 
 ## Client Redirect URI Security
 

docs/v2/servers/composition.mdx

@@ -35,11 +35,11 @@ The choice of importing or mounting depends on your use case and requirements.
 
 ### Proxy Servers
 
-FastMCP supports [MCP proxying](/servers/proxy), which allows you to mirror a local or remote server in a local FastMCP instance. Proxies are fully compatible with both importing and mounting.
+FastMCP supports [MCP proxying](/v2/servers/proxy), which allows you to mirror a local or remote server in a local FastMCP instance. Proxies are fully compatible with both importing and mounting.
 
 <VersionBadge version="2.4.0" />
 
-You can also create proxies from configuration dictionaries that follow the MCPConfig schema, which is useful for quickly connecting to one or more remote servers. See the [Proxy Servers documentation](/servers/proxy#configuration-based-proxies) for details on configuration-based proxying. Note that MCPConfig follows an emerging standard and its format may evolve over time.
+You can also create proxies from configuration dictionaries that follow the MCPConfig schema, which is useful for quickly connecting to one or more remote servers. See the [Proxy Servers documentation](/v2/servers/proxy#configuration-based-proxies) for details on configuration-based proxying. Note that MCPConfig follows an emerging standard and its format may evolve over time.
 
 Prefixing rules for tools, prompts, resources, and templates are identical across importing, mounting, and proxies. When prefixes are used, resource URIs are prefixed using path format (since 2.4.0): `resource://prefix/path/to/resource`.
 

docs/v2/servers/context.mdx

@@ -6,7 +6,7 @@ icon: rectangle-code
 ---
 import { VersionBadge } from '/snippets/version-badge.mdx'
 
-When defining FastMCP [tools](/servers/tools), [resources](/servers/resources), resource templates, or [prompts](/servers/prompts), your functions might need to interact with the underlying MCP session or access advanced server capabilities. FastMCP provides the `Context` object for this purpose.
+When defining FastMCP [tools](/v2/servers/tools), [resources](/v2/servers/resources), resource templates, or [prompts](/v2/servers/prompts), your functions might need to interact with the underlying MCP session or access advanced server capabilities. FastMCP provides the `Context` object for this purpose.
 
 <Note>
 FastMCP uses [Docket](https://github.com/chrisguidry/docket)'s dependency injection system for managing runtime dependencies. This page covers Context and the built-in dependencies; see [Custom Dependencies](#custom-dependencies) for creating your own.
@@ -135,7 +135,7 @@ await ctx.warning("Deprecated parameter used")
 await ctx.error("Processing failed")
 ```
 
-See [Server Logging](/servers/logging) for complete documentation and examples.
+See [Server Logging](/v2/servers/logging) for complete documentation and examples.
 ### Client Elicitation
 
 <VersionBadge version="2.10.0" />
@@ -148,7 +148,7 @@ if result.action == "accept":
     name = result.data
 ```
 
-See [User Elicitation](/servers/elicitation) for detailed examples and supported response types.
+See [User Elicitation](/v2/servers/elicitation) for detailed examples and supported response types.
 
 ### LLM Sampling
 
@@ -160,7 +160,7 @@ Request the client's LLM to generate text based on provided messages, useful for
 response = await ctx.sample("Analyze this data", temperature=0.7)
 ```
 
-See [LLM Sampling](/servers/sampling) for comprehensive usage and advanced techniques.
+See [LLM Sampling](/v2/servers/sampling) for comprehensive usage and advanced techniques.
 
 
 ### Progress Reporting
@@ -171,7 +171,7 @@ Update clients on the progress of long-running operations, enabling progress ind
 await ctx.report_progress(progress=50, total=100)  # 50% complete
 ```
 
-See [Progress Reporting](/servers/progress) for detailed patterns and examples.
+See [Progress Reporting](/v2/servers/progress) for detailed patterns and examples.
 
 ### Resource Access
 
@@ -213,7 +213,7 @@ messages = result.messages
 
 <VersionBadge version="2.11.0" />
 
-Store and share data between middleware and handlers within a single MCP request. Each MCP request (such as calling a tool, reading a resource, listing tools, or listing resources) receives its own context object with isolated state. Context state is particularly useful for passing information from [middleware](/servers/middleware) to your handlers.
+Store and share data between middleware and handlers within a single MCP request. Each MCP request (such as calling a tool, reading a resource, listing tools, or listing resources) receives its own context object with isolated state. Context state is particularly useful for passing information from [middleware](/v2/servers/middleware) to your handlers.
 
 To store a value in the context state, use `ctx.set_state(key, value)`. To retrieve a value, use `ctx.get_state(key)`.
 

docs/v2/servers/elicitation.mdx

@@ -457,6 +457,6 @@ async def plan_meeting(ctx: Context) -> str:
 
 ## Client Requirements
 
-Elicitation requires the client to implement an elicitation handler. See [Client Elicitation](/clients/elicitation) for details on how clients can handle these requests.
+Elicitation requires the client to implement an elicitation handler. See [Client Elicitation](/v2/clients/elicitation) for details on how clients can handle these requests.
 
 If a client doesn't support elicitation, calls to `ctx.elicit()` will raise an error indicating that elicitation is not supported.

docs/v2/servers/logging.mdx

@@ -246,4 +246,4 @@ Log messages are sent to the client through the MCP protocol. How clients handle
 - **Production clients**: May store logs for later analysis or display to users
 - **Integration clients**: May forward logs to external logging systems
 
-See [Client Logging](/clients/logging) for details on how clients can handle server log messages.
+See [Client Logging](/v2/clients/logging) for details on how clients can handle server log messages.

docs/v2/servers/middleware.mdx

@@ -46,7 +46,7 @@ The key insight is that middleware forms a chain where each piece decides whethe
 
 If you're familiar with ASGI middleware, the basic structure of FastMCP middleware will feel familiar. At its core, middleware is a callable class that receives a context object containing information about the current JSON-RPC message and a handler function to continue the middleware chain.
 
-It's important to understand that MCP operates on the [JSON-RPC specification](https://spec.modelcontextprotocol.io/specification/basic/transports/). While FastMCP presents requests and responses in a familiar way, these are fundamentally JSON-RPC messages, not HTTP request/response pairs like you might be used to in web applications. FastMCP middleware works with all [transport types](/clients/transports), including local stdio transport and HTTP transports, though not all middleware implementations are compatible across all transports (e.g., middleware that inspects HTTP headers won't work with stdio transport).
+It's important to understand that MCP operates on the [JSON-RPC specification](https://spec.modelcontextprotocol.io/specification/basic/transports/). While FastMCP presents requests and responses in a familiar way, these are fundamentally JSON-RPC messages, not HTTP request/response pairs like you might be used to in web applications. FastMCP middleware works with all [transport types](/v2/clients/transports), including local stdio transport and HTTP transports, though not all middleware implementations are compatible across all transports (e.g., middleware that inspects HTTP headers won't work with stdio transport).
 
 The most fundamental way to implement middleware is by overriding the `__call__` method on the `Middleware` base class:
 
@@ -166,7 +166,7 @@ class SessionAwareMiddleware(Middleware):
         return await call_next(context)
 ```
 
-For HTTP request data (headers, client IP, etc.) when using HTTP transports, use `get_http_request()` or `get_http_headers()` from `fastmcp.server.dependencies`, which work regardless of MCP session availability. See [HTTP Requests](/servers/context#http-requests) for details.
+For HTTP request data (headers, client IP, etc.) when using HTTP transports, use `get_http_request()` or `get_http_headers()` from `fastmcp.server.dependencies`, which work regardless of MCP session availability. See [HTTP Requests](/v2/servers/context#http-requests) for details.
 
 ## Component Access in Middleware
 
@@ -324,7 +324,7 @@ class ToolCallMiddleware(Middleware):
 ```
 
 <Tip>
-For more complex tool rewriting scenarios, consider using [Tool Transformation](/patterns/tool-transformation) patterns which provide a more structured approach to creating modified tool variants.
+For more complex tool rewriting scenarios, consider using [Tool Transformation](/v2/patterns/tool-transformation) patterns which provide a more structured approach to creating modified tool variants.
 </Tip>
 
 ### Anatomy of a Hook
@@ -373,7 +373,7 @@ You have complete control over the request flow:
 
 <VersionBadge version="2.11.0" />
 
-In addition to modifying the request and response, you can also store state data that your tools can (optionally) access later. To do so, use the FastMCP Context to either `set_state` or `get_state` as appropriate. For more information, see the [Context State Management](/servers/context#state-management) docs.
+In addition to modifying the request and response, you can also store state data that your tools can (optionally) access later. To do so, use the FastMCP Context to either `set_state` or `get_state` as appropriate. For more information, see the [Context State Management](/v2/servers/context#state-management) docs.
 
 ## Creating Middleware
 
@@ -436,7 +436,7 @@ This creates the following execution flow:
 
 ## Server Composition and Middleware
 
-When using [Server Composition](/servers/composition) with `mount` or `import_server`, middleware behavior follows these rules:
+When using [Server Composition](/v2/servers/composition) with `mount` or `import_server`, middleware behavior follows these rules:
 
 1. **Parent server middleware** runs for all requests, including those routed to mounted servers
 2. **Mounted server middleware** only runs for requests handled by that specific server
@@ -556,7 +556,7 @@ from fastmcp.server.middleware.caching import ResponseCachingMiddleware
 mcp.add_middleware(ResponseCachingMiddleware())
 ```
 
-Out of the box, it caches call/list tool, resources, and prompts to an in-memory cache with TTL-based expiration. Cache entries expire based on their TTL; there is no event-based cache invalidation. List calls are stored under global keys—when sharing a storage backend across multiple servers, consider namespacing collections to prevent conflicts. See [Storage Backends](/servers/storage-backends) for advanced configuration options.
+Out of the box, it caches call/list tool, resources, and prompts to an in-memory cache with TTL-based expiration. Cache entries expire based on their TTL; there is no event-based cache invalidation. List calls are stored under global keys—when sharing a storage backend across multiple servers, consider namespacing collections to prevent conflicts. See [Storage Backends](/v2/servers/storage-backends) for advanced configuration options.
 
 Each method can be configured individually, for example, caching list tools for 30 seconds, limiting caching to specific tools, and disabling caching for resource reads:
 
@@ -578,7 +578,7 @@ mcp.add_middleware(ResponseCachingMiddleware(
 
 #### Storage Backends
 
-By default, caching uses in-memory storage, which is fast but doesn't persist across restarts. For production or persistent caching across server restarts, configure a different storage backend. See [Storage Backends](/servers/storage-backends) for complete options including disk, Redis, DynamoDB, and custom implementations.
+By default, caching uses in-memory storage, which is fast but doesn't persist across restarts. For production or persistent caching across server restarts, configure a different storage backend. See [Storage Backends](/v2/servers/storage-backends) for complete options including disk, Redis, DynamoDB, and custom implementations.
 
 Disk-based caching example:
 

docs/v2/servers/progress.mdx

@@ -186,4 +186,4 @@ Progress reporting requires clients to support progress handling:
 
 - Clients must send a `progressToken` in the initial request to receive progress updates
 - If no progress token is provided, progress calls will have no effect (they won't error)
-- See [Client Progress](/clients/progress) for details on implementing client-side progress handling
+- See [Client Progress](/v2/clients/progress) for details on implementing client-side progress handling

docs/v2/servers/prompts.mdx

@@ -100,7 +100,7 @@ def data_analysis_prompt(
 <ParamField body="icons" type="list[Icon] | None">
   <VersionBadge version="2.13.0" />
 
-  Optional list of icon representations for this prompt. See [Icons](/servers/icons) for detailed examples
+  Optional list of icon representations for this prompt. See [Icons](/v2/servers/icons) for detailed examples
 </ParamField>
 
 <ParamField body="meta" type="dict[str, Any] | None">
@@ -297,7 +297,7 @@ async def generate_report_request(report_type: str, ctx: Context) -> str:
     return f"Please create a {report_type} report. Request ID: {ctx.request_id}"
 ```
 
-For full documentation on the Context object and all its capabilities, see the [Context documentation](/servers/context).
+For full documentation on the Context object and all its capabilities, see the [Context documentation](/v2/servers/context).
 
 ### Notifications
 
@@ -318,7 +318,7 @@ example_prompt.enable()         # Sends prompts/list_changed notification
 
 Notifications are only sent when these operations occur within an active MCP request context (e.g., when called from within a tool or other MCP operation). Operations performed during server initialization do not trigger notifications.
 
-Clients can handle these notifications using a [message handler](/clients/messages) to automatically refresh their prompt lists or update their interfaces.
+Clients can handle these notifications using a [message handler](/v2/clients/messages) to automatically refresh their prompt lists or update their interfaces.
 
 ## Server Behavior
 

docs/v2/servers/proxy.mdx

@@ -42,7 +42,7 @@ sequenceDiagram
 
 When using proxy servers, especially those connecting to HTTP-based backend servers, be aware that latency can be significant. Operations like `list_tools()` may take hundreds of milliseconds compared to 1-2ms for local tools. When mounting proxy servers, this latency affects all operations on the parent server, not just interactions with the proxied tools.
 
-If low latency is a requirement for your use-case, consider using [`import_server()`](/servers/composition#importing-static-composition) to copy tools at startup rather than proxying them at runtime.
+If low latency is a requirement for your use-case, consider using [`import_server()`](/v2/servers/composition#importing-static-composition) to copy tools at startup rather than proxying them at runtime.
 
 ## Quick Start
 
@@ -71,7 +71,7 @@ This single setup gives you:
 - Session isolation to prevent context mixing
 - Full compatibility with all MCP clients
 
-You can also pass a FastMCP [client transport](/clients/transports) (or parameter that can be inferred to a transport) to `as_proxy()`. This will automatically create a `ProxyClient` instance for you.
+You can also pass a FastMCP [client transport](/v2/clients/transports) (or parameter that can be inferred to a transport) to `as_proxy()`. This will automatically create a `ProxyClient` instance for you.
 
 Finally, you can pass a regular FastMCP `Client` instance to `as_proxy()`. This will work for many use cases, but may break if advanced MCP features like sampling or elicitation are invoked by the server. 
 

docs/v2/servers/resources.mdx

@@ -109,7 +109,7 @@ def get_application_status() -> dict:
 <ParamField body="icons" type="list[Icon] | None">
   <VersionBadge version="2.13.0" />
 
-  Optional list of icon representations for this resource or template. See [Icons](/servers/icons) for detailed examples
+  Optional list of icon representations for this resource or template. See [Icons](/v2/servers/icons) for detailed examples
 </ParamField>
 
 <ParamField body="annotations" type="Annotations | dict | None">
@@ -195,7 +195,7 @@ async def get_details(name: str, ctx: Context) -> dict:
     }
 ```
 
-For full documentation on the Context object and all its capabilities, see the [Context documentation](/servers/context).
+For full documentation on the Context object and all its capabilities, see the [Context documentation](/v2/servers/context).
 
 
 ### Async Resources
@@ -323,7 +323,7 @@ example_resource.enable()           # Sends resources/list_changed notification
 
 Notifications are only sent when these operations occur within an active MCP request context (e.g., when called from within a tool or other MCP operation). Operations performed during server initialization do not trigger notifications.
 
-Clients can handle these notifications using a [message handler](/clients/messages) to automatically refresh their resource lists or update their interfaces.
+Clients can handle these notifications using a [message handler](/v2/clients/messages) to automatically refresh their resource lists or update their interfaces.
 
 ### Annotations
 

docs/v2/servers/sampling.mdx

@@ -443,7 +443,7 @@ tool_result = ToolResultContent(
 
 Client support for sampling is optional—some clients may not implement it. To ensure your tools work regardless of client capabilities, configure a `sampling_handler` that sends requests directly to an LLM provider.
 
-FastMCP provides built-in handlers for [OpenAI and Anthropic APIs](/clients/sampling#built-in-handlers). These handlers support the full sampling API including tools, automatically converting your Python functions to each provider's format.
+FastMCP provides built-in handlers for [OpenAI and Anthropic APIs](/v2/clients/sampling#built-in-handlers). These handlers support the full sampling API including tools, automatically converting your Python functions to each provider's format.
 
 <Note>
 Install handlers with `pip install fastmcp[openai]` or `pip install fastmcp[anthropic]`.

docs/v2/servers/server.mdx

@@ -53,11 +53,11 @@ The `FastMCP` constructor accepts several arguments:
 <ParamField body="icons" type="list[Icon] | None">
   <VersionBadge version="2.13.0" />
 
-  List of icon representations for your server. Icons help users visually identify your server in client applications. See [Icons](/servers/icons) for detailed examples
+  List of icon representations for your server. Icons help users visually identify your server in client applications. See [Icons](/v2/servers/icons) for detailed examples
 </ParamField>
 
 <ParamField body="auth" type="OAuthProvider | TokenVerifier | None">
-  Authentication provider for securing HTTP-based transports. See [Authentication](/servers/auth/authentication) for configuration options
+  Authentication provider for securing HTTP-based transports. See [Authentication](/v2/servers/auth/authentication) for configuration options
 </ParamField>
 
 <ParamField body="lifespan" type="AsyncContextManager | None">
@@ -92,7 +92,7 @@ The `FastMCP` constructor accepts several arguments:
 
 <ParamField body="strict_input_validation" type="bool" default="False">
   <VersionBadge version="2.13.0" />
-  Controls how tool input parameters are validated. When `False` (default), FastMCP uses Pydantic's flexible validation that coerces compatible inputs (e.g., `"10"` → `10` for int parameters). When `True`, uses the MCP SDK's JSON Schema validation to validate inputs against the exact schema before passing them to your function, rejecting any type mismatches. The default mode improves compatibility with LLM clients while maintaining type safety. See [Input Validation Modes](/servers/tools#input-validation-modes) for details
+  Controls how tool input parameters are validated. When `False` (default), FastMCP uses Pydantic's flexible validation that coerces compatible inputs (e.g., `"10"` → `10` for int parameters). When `True`, uses the MCP SDK's JSON Schema validation to validate inputs against the exact schema before passing them to your function, rejecting any type mismatches. The default mode improves compatibility with LLM clients while maintaining type safety. See [Input Validation Modes](/v2/servers/tools#input-validation-modes) for details
 </ParamField>
 
 <ParamField body="include_fastmcp_meta" type="bool" default="True">
@@ -116,7 +116,7 @@ def multiply(a: float, b: float) -> float:
     return a * b
 ```
 
-See [Tools](/servers/tools) for detailed documentation.
+See [Tools](/v2/servers/tools) for detailed documentation.
 
 ### Resources
 
@@ -129,7 +129,7 @@ def get_config() -> dict:
     return {"theme": "dark", "version": "1.0"}
 ```
 
-See [Resources & Templates](/servers/resources) for detailed documentation.
+See [Resources & Templates](/v2/servers/resources) for detailed documentation.
 
 ### Resource Templates
 
@@ -143,7 +143,7 @@ def get_user_profile(user_id: int) -> dict:
     return {"id": user_id, "name": f"User {user_id}", "status": "active"}
 ```
 
-See [Resources & Templates](/servers/resources) for detailed documentation.
+See [Resources & Templates](/v2/servers/resources) for detailed documentation.
 
 ### Prompts
 
@@ -157,7 +157,7 @@ def analyze_data(data_points: list[float]) -> str:
     return f"Please analyze these data points: {formatted_data}"
 ```
 
-See [Prompts](/servers/prompts) for detailed documentation.
+See [Prompts](/v2/servers/prompts) for detailed documentation.
 
 ## Tag-Based Filtering
 
@@ -232,7 +232,7 @@ FastMCP supports several transport options:
 
 The server can also be run using the FastMCP CLI.
 
-For detailed information on each transport, how to configure them (host, port, paths), and when to use which, please refer to the [**Running Your FastMCP Server**](/deployment/running-server) guide.
+For detailed information on each transport, how to configure them (host, port, paths), and when to use which, please refer to the [**Running Your FastMCP Server**](/v2/deployment/running-server) guide.
 
 ## Custom Routes
 
@@ -258,7 +258,7 @@ Custom routes are served alongside your MCP endpoint and are useful for:
 - Simple status or info endpoints
 - Basic webhooks or callbacks
 
-For more complex web applications, consider [mounting your MCP server into a FastAPI or Starlette app](/deployment/http#integration-with-web-frameworks).
+For more complex web applications, consider [mounting your MCP server into a FastAPI or Starlette app](/v2/deployment/http#integration-with-web-frameworks).
 
 ## Composing Servers
 
@@ -266,7 +266,7 @@ For more complex web applications, consider [mounting your MCP server into a Fas
 
 FastMCP supports composing multiple servers together using `import_server` (static copy) and `mount` (live link). This allows you to organize large applications into modular components or reuse existing servers.
 
-See the [Server Composition](/servers/composition) guide for full details, best practices, and examples.
+See the [Server Composition](/v2/servers/composition) guide for full details, best practices, and examples.
 
 ```python
 # Example: Importing a subserver
@@ -292,7 +292,7 @@ FastMCP can act as a proxy for any MCP server (local or remote) using `FastMCP.a
 
 Proxies automatically handle concurrent operations safely by creating fresh sessions for each request when using disconnected clients.
 
-See the [Proxying Servers](/servers/proxy) guide for details and advanced usage.
+See the [Proxying Servers](/v2/servers/proxy) guide for details and advanced usage.
 
 ```python
 from fastmcp import FastMCP, Client
@@ -308,7 +308,7 @@ proxy = FastMCP.as_proxy(backend, name="ProxyServer")
 
 FastMCP can automatically generate servers from OpenAPI specifications or existing FastAPI applications using `FastMCP.from_openapi()` and `FastMCP.from_fastapi()`. This allows you to instantly convert existing APIs into MCP servers without manual tool creation.
 
-See the [FastAPI Integration](/integrations/fastapi) and [OpenAPI Integration](/integrations/openapi) guides for detailed examples and configuration options.
+See the [FastAPI Integration](/v2/integrations/fastapi) and [OpenAPI Integration](/v2/integrations/openapi) guides for detailed examples and configuration options.
 
 ```python
 import httpx
@@ -364,7 +364,7 @@ print(fastmcp.settings.include_fastmcp_meta)   # Default: True
 Common global settings include:
 - **`log_level`**: Logging level ("DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"), set with `FASTMCP_LOG_LEVEL`
 - **`mask_error_details`**: Whether to hide detailed error information from clients, set with `FASTMCP_MASK_ERROR_DETAILS`
-- **`strict_input_validation`**: Controls tool input validation mode (default: False for flexible coercion), set with `FASTMCP_STRICT_INPUT_VALIDATION`. See [Input Validation Modes](/servers/tools#input-validation-modes)
+- **`strict_input_validation`**: Controls tool input validation mode (default: False for flexible coercion), set with `FASTMCP_STRICT_INPUT_VALIDATION`. See [Input Validation Modes](/v2/servers/tools#input-validation-modes)
 - **`include_fastmcp_meta`**: Whether to include FastMCP metadata in component responses (default: True), set with `FASTMCP_INCLUDE_FASTMCP_META`
 - **`env_file`**: Path to the environment file to load settings from (default: ".env"), set with `FASTMCP_ENV_FILE`. Useful when your project uses a `.env` file with syntax incompatible with python-dotenv
 

docs/v2/servers/storage-backends.mdx

@@ -151,7 +151,7 @@ Before using these backends in production, review the [py-key-value documentatio
 
 ### Server-Side OAuth Token Storage
 
-The [OAuth Proxy](/servers/auth/oauth-proxy) and OAuth auth providers use storage for persisting OAuth client registrations and upstream tokens. **By default, storage is automatically encrypted using `FernetEncryptionWrapper`.** When providing custom storage, wrap it in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest.
+The [OAuth Proxy](/v2/servers/auth/oauth-proxy) and OAuth auth providers use storage for persisting OAuth client registrations and upstream tokens. **By default, storage is automatically encrypted using `FernetEncryptionWrapper`.** When providing custom storage, wrap it in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest.
 
 **Development (default behavior):**
 
@@ -196,11 +196,11 @@ auth = GitHubProvider(
 )
 ```
 
-Both parameters are required for production. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. See [OAuth Token Security](/deployment/http#oauth-token-security) and [Key and Storage Management](/servers/auth/oauth-proxy#key-and-storage-management) for complete setup details.
+Both parameters are required for production. **Wrap your storage in `FernetEncryptionWrapper` to encrypt sensitive OAuth tokens at rest** - without it, tokens are stored in plaintext. See [OAuth Token Security](/v2/deployment/http#oauth-token-security) and [Key and Storage Management](/v2/servers/auth/oauth-proxy#key-and-storage-management) for complete setup details.
 
 ### Response Caching Middleware
 
-The [Response Caching Middleware](/servers/middleware#caching-middleware) caches tool calls, resource reads, and prompt requests. Storage configuration is passed via the `cache_storage` parameter:
+The [Response Caching Middleware](/v2/servers/middleware#caching-middleware) caches tool calls, resource reads, and prompt requests. Storage configuration is passed via the `cache_storage` parameter:
 
 ```python
 from fastmcp import FastMCP
@@ -233,7 +233,7 @@ middleware = ResponseCachingMiddleware(cache_storage=namespaced_store)
 
 ### Client-Side OAuth Token Storage
 
-The [FastMCP Client](/clients/client) uses storage for persisting OAuth tokens locally. By default, tokens are stored in memory:
+The [FastMCP Client](/v2/clients/client) uses storage for persisting OAuth tokens locally. By default, tokens are stored in memory:
 
 ```python
 from fastmcp.client.auth import OAuthClientProvider
@@ -270,6 +270,6 @@ This allows clients to reconnect without re-authenticating after restarts.
 ## More Resources
 
 - [py-key-value-aio GitHub](https://github.com/strawgate/py-key-value) - Full library documentation
-- [Response Caching Middleware](/servers/middleware#caching-middleware) - Using storage for caching
-- [OAuth Token Security](/deployment/http#oauth-token-security) - Production OAuth configuration
-- [HTTP Deployment](/deployment/http) - Complete deployment guide
+- [Response Caching Middleware](/v2/servers/middleware#caching-middleware) - Using storage for caching
+- [OAuth Token Security](/v2/deployment/http#oauth-token-security) - Production OAuth configuration
+- [HTTP Deployment](/v2/deployment/http) - Complete deployment guide

docs/v2/servers/tools.mdx

@@ -84,7 +84,7 @@ def search_products_implementation(query: str, category: str | None = None) -> l
 <ParamField body="icons" type="list[Icon] | None">
   <VersionBadge version="2.13.0" />
 
-  Optional list of icon representations for this tool. See [Icons](/servers/icons) for detailed examples
+  Optional list of icon representations for this tool. See [Icons](/v2/servers/icons) for detailed examples
 </ParamField>
 
 <ParamField body="annotations" type="ToolAnnotations | dict | None">
@@ -366,7 +366,7 @@ def get_user_details(user_id: str = Depends(get_user_id)) -> str:
     return f"Details for {user_id}"
 ```
 
-See [Custom Dependencies](/servers/context#custom-dependencies) for more details on dependency injection.
+See [Custom Dependencies](/v2/servers/context#custom-dependencies) for more details on dependency injection.
 
 ## Return Values
 
@@ -867,7 +867,7 @@ def delete_user(user_id: str) -> dict:
 For tools that write to databases, send notifications, create/update/delete resources, or trigger workflows, omit `readOnlyHint` or set it to `False`. Use `destructiveHint=True` for operations that cannot be undone.
 
 Client-specific behavior:
-- **ChatGPT**: Skips confirmation prompts for read-only tools in Chat mode (see [ChatGPT integration](/integrations/chatgpt))
+- **ChatGPT**: Skips confirmation prompts for read-only tools in Chat mode (see [ChatGPT integration](/v2/integrations/chatgpt))
 - **Claude**: Uses hints to understand tool safety profiles and make better execution decisions
 
 ## Notifications
@@ -890,7 +890,7 @@ mcp.remove_tool("example_tool") # Sends tools/list_changed notification
 
 Notifications are only sent when these operations occur within an active MCP request context (e.g., when called from within a tool or other MCP operation). Operations performed during server initialization do not trigger notifications.
 
-Clients can handle these notifications using a [message handler](/clients/messages) to automatically refresh their tool lists or update their interfaces.
+Clients can handle these notifications using a [message handler](/v2/clients/messages) to automatically refresh their tool lists or update their interfaces.
 
 ## Accessing the MCP Context
 
@@ -931,7 +931,7 @@ The Context object provides access to:
 - **LLM Sampling**: `ctx.sample(...)`
 - **Request Information**: `ctx.request_id`, `ctx.client_id`
 
-For full documentation on the Context object and all its capabilities, see the [Context documentation](/servers/context).
+For full documentation on the Context object and all its capabilities, see the [Context documentation](/v2/servers/context).
 
 ## Server Behavior
 

docs/v2/tutorials/create-mcp-server.mdx

@@ -17,7 +17,7 @@ Every code block in this tutorial is a complete, runnable example. You can copy
 
 ### Prerequisites
 
-Make sure you have FastMCP installed. If not, follow the [installation guide](/getting-started/installation).
+Make sure you have FastMCP installed. If not, follow the [installation guide](/v2/getting-started/installation).
 
 ```bash
 pip install fastmcp
@@ -152,7 +152,7 @@ Now you can run your server from the command line:
 ```bash
 python my_mcp_server.py
 ```
-This starts the server using the default **STDIO transport**, which is how clients like Claude Desktop communicate with local servers. To learn about other transports, like HTTP, see the [Running Your Server](/deployment/running-server) guide.
+This starts the server using the default **STDIO transport**, which is how clients like Claude Desktop communicate with local servers. To learn about other transports, like HTTP, see the [Running Your Server](/v2/deployment/running-server) guide.
 
 ## The Complete Server
 
@@ -191,8 +191,8 @@ if __name__ == "__main__":
 
 You've successfully built an MCP server! From here, you can explore more advanced topics:
 
--   [**Tools in Depth**](/servers/tools): Learn about asynchronous tools, error handling, and custom return types.
--   [**Resources & Templates**](/servers/resources): Discover different resource types, including files and HTTP endpoints.
--   [**Prompts**](/servers/prompts): Create reusable prompt templates for your LLM.
--   [**Running Your Server**](/deployment/running-server): Deploy your server with different transports like HTTP.
+-   [**Tools in Depth**](/v2/servers/tools): Learn about asynchronous tools, error handling, and custom return types.
+-   [**Resources & Templates**](/v2/servers/resources): Discover different resource types, including files and HTTP endpoints.
+-   [**Prompts**](/v2/servers/prompts): Create reusable prompt templates for your LLM.
+-   [**Running Your Server**](/v2/deployment/running-server): Deploy your server with different transports like HTTP.
 

docs/v2/tutorials/mcp.mdx

@@ -49,7 +49,7 @@ def get_weather(city: str) -> dict:
     return {"city": city, "temperature": "72F", "forecast": "Sunny"}
 ```
 
-[**Learn more about Tools →**](/servers/tools)
+[**Learn more about Tools →**](/v2/servers/tools)
 
 ### Resources: Read-Only Data
 
@@ -86,7 +86,7 @@ def get_user_profile(user_id: str) -> dict:
     return {"id": user_id, "name": "Zaphod Beeblebrox"}
 ```
 
-[**Learn more about Resources & Templates →**](/servers/resources)
+[**Learn more about Resources & Templates →**](/v2/servers/resources)
 
 ### Prompts: Reusable Instructions
 
@@ -107,7 +107,7 @@ def summarize_text(text_to_summarize: str) -> str:
         """
 ```
 
-[**Learn more about Prompts →**](/servers/prompts)
+[**Learn more about Prompts →**](/v2/servers/prompts)
 
 ## Advanced Capabilities
 
@@ -117,4 +117,4 @@ Beyond the core components, MCP also supports more advanced interaction patterns
 
 Now that you understand the core concepts of the Model Context Protocol, you're ready to start building. The best place to begin is our step-by-step tutorial.
 
-[**Tutorial: How to Create an MCP Server in Python →**](/tutorials/create-mcp-server)
+[**Tutorial: How to Create an MCP Server in Python →**](/v2/tutorials/create-mcp-server)

docs/v2/tutorials/rest-api.mdx

@@ -17,7 +17,7 @@ Every code block in this tutorial is a complete, runnable example. You can copy
 
 ### Prerequisites
 
-Make sure you have FastMCP installed. If not, follow the [installation guide](/getting-started/installation).
+Make sure you have FastMCP installed. If not, follow the [installation guide](/v2/getting-started/installation).
 
 ```bash
 pip install fastmcp
@@ -35,7 +35,7 @@ For this tutorial, we'll use the [JSONPlaceholder API](https://jsonplaceholder.t
 Now for the magic. We'll use `FastMCP.from_openapi`. This method takes an `httpx.AsyncClient` configured for your API and its OpenAPI specification, and automatically converts **every endpoint** into a callable MCP `Tool`.
 
 <Tip>
-Learn more about working with OpenAPI specs in the [OpenAPI integration docs](/integrations/openapi).
+Learn more about working with OpenAPI specs in the [OpenAPI integration docs](/v2/integrations/openapi).
 </Tip>
 
 <Note>
@@ -92,7 +92,7 @@ And that's it! With just a few lines of code, you've created an MCP server that
 Let's verify that our new MCP server works. We can use the `fastmcp.Client` to connect to it and inspect its tools.
 
 <Tip>
-Learn more about the FastMCP client in the [client docs](/clients/client).
+Learn more about the FastMCP client in the [client docs](/v2/clients/client).
 </Tip>
 
 Create a separate file, `api_client.py`:
@@ -144,7 +144,7 @@ However, for clients that support the full MCP spec, representing `GET` requests
 FastMCP allows users to customize this behavior using the concept of "route maps". A `RouteMap` is a mapping of an API route to an MCP type. FastMCP checks each API route against your custom maps in order. If a route matches a map, it's converted to the specified `mcp_type`. Any route that doesn't match your custom maps will fall back to the default behavior (becoming a `Tool`).
 
 <Tip>
-Learn more about route maps in the [OpenAPI integration docs](/integrations/openapi#route-mapping).
+Learn more about route maps in the [OpenAPI integration docs](/v2/integrations/openapi#route-mapping).
 </Tip>
 
 Here’s how you can add custom route maps to turn `GET` requests into `Resources` and `ResourceTemplates` (if they have path parameters):