Redirects, broken links from structure changes

Author: irvinebroque

public/_redirects

@@ -108,7 +108,7 @@
 /agents/examples/sdk/ /agents/api-reference/agents-api/ 301
 /agents/examples/build-mcp-server/ /agents/api-reference/build-mcp-server/ 301
 /agents/api-reference/build-mcp-server/ /agents/guides/build-mcp-server/ 301
-
+/agents/guides/build-mcp-server/ /agents/guides/remote-mcp-server/ 301
 
 # ai
 /ai/ /use-cases/ai/ 301

src/content/docs/agents/guides/remote-mcp-server.mdx

@@ -15,7 +15,7 @@ The link below will guide you through everything you need to do to deploy this [
 
 [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create/deploy-to-workers&repository=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-server)
 
-At the end of this process, you will have a new git repository on your GitHub or GitLab account for your MCP server, configured to automatically deploy Cloudflare each time you push a change or merge a pull request to the main branch of the repository. You can then clone this repository, [develop locally](/agents/model-context-protocol/getting-started/#local-development), and start writing code and building.
+At the end of this process, you will have a new git repository on your GitHub or GitLab account for your MCP server, configured to automatically deploy Cloudflare each time you push a change or merge a pull request to the main branch of the repository. You can then clone this repository, [develop locally](/agents/guides/remote-mcp-server/#local-development), and start writing code and building.
 
 Alternatively, you can use the command line as shown below to create a new MCP Server on your local machine.
 
@@ -219,7 +219,7 @@ wrangler secret put GITHUB_CLIENT_SECRET
 
 #### Finally, connect to your MCP server
 
-Now that you've added the ID and secret of your production OAuth app, you should now be able to connect to your MCP server running at `worker-name.account-name.workers.dev/sse` using the MCP inspector or ([other MCP clients](/agents/model-context-protocol/getting-started/#connect-your-mcp-server-to-claude-and-other-mcp-clients)), and authenticate with GitHub.
+Now that you've added the ID and secret of your production OAuth app, you should now be able to connect to your MCP server running at `worker-name.account-name.workers.dev/sse` using the MCP inspector or ([other MCP clients](/agents/guides/remote-mcp-server/#connect-your-mcp-server-to-claude-and-other-mcp-clients)), and authenticate with GitHub.
 
 ## Next steps
 

src/content/docs/agents/model-context-protocol/authorization.mdx

@@ -20,8 +20,8 @@ Cloudflare provides an [OAuth Provider Library](https://github.com/cloudflare/wo
 
 You can use the OAuth Provider Library in three ways:
 
-1. **Your Worker handles authorization itself.** Your MCP server, running on Cloudflare, handles the complete OAuth flow. ([Example](/agents/model-context-protocol/getting-started/))
-2. **Integrate directly with a third-party OAuth provider**, such as GitHub or Google. ([Example](/agents/guides/remote-mcp-server-github/))
+1. **Your Worker handles authorization itself.** Your MCP server, running on Cloudflare, handles the complete OAuth flow. ([Example](/agents/guides/remote-mcp-server/))
+2. **Integrate directly with a third-party OAuth provider**, such as GitHub or Google.
 3. **Integrate with your own OAuth provider**, including authorization-as-a-service providers you might already rely on, such as Stytch and Auth0.
 
 The following sections describe each of these options and link to runnable code examples for each.
@@ -49,7 +49,7 @@ export default new OAuthProvider({
 });
 ```
 
-Refer to the [getting started example](/agents/model-context-protocol/getting-started/) for a complete example of the `OAuthProvider` in use, with a mock authentication flow.
+Refer to the [getting started example](/agents/guides/remote-mcp-server/) for a complete example of the `OAuthProvider` in use, with a mock authentication flow.
 
 The authorization flow in this case works like this:
 
@@ -73,11 +73,11 @@ sequenceDiagram
     Note over C,M: Begin standard MCP message exchange
 ```
 
-Remember — [authentication is different from authorization](https://www.cloudflare.com/learning/access-management/authn-vs-authz/). Your MCP Server can handle authorization itself, while still relying on an external authentication service to first authenticate users. The [example](/agents/model-context-protocol/getting-started) in getting started provides a mock authentdcation flow. You will need to implement your own authentication handler — either handling authentication yourself, or using an external authentication services.
+Remember — [authentication is different from authorization](https://www.cloudflare.com/learning/access-management/authn-vs-authz/). Your MCP Server can handle authorization itself, while still relying on an external authentication service to first authenticate users. The [example](/agents/guides/remote-mcp-server) in getting started provides a mock authentdcation flow. You will need to implement your own authentication handler — either handling authentication yourself, or using an external authentication services.
 
 ### (2) Third-party OAuth Provider
 
-The [OAuth Provider Library](https://github.com/cloudflare/workers-oauth-provider) can be configured to use a third-party OAuth provider, such as GitHub or Google. You can see a complete example of this in the [GitHub example](/agents/guides/remote-mcp-server-github).
+The [OAuth Provider Library](https://github.com/cloudflare/workers-oauth-provider) can be configured to use a third-party OAuth provider, such as GitHub or Google. You can see a complete example of this in the [GitHub example](/agents/guides/remote-mcp-server/#add-authentication).
 
 When you use a third-party OAuth provider, you must provide a handler to the `OAuthProvider` that implements the OAuth flow for the third-party provider.
 
@@ -129,4 +129,4 @@ If your application already implements an Oauth Provider itself, or you use Styt
 ## Next steps
 
 - [Learn how to use the Workers OAuth Provider Library](https://github.com/cloudflare/workers-oauth-provider)
-- Learn how to use a third-party OAuth provider, using the [GitHub](/agents/guides/remote-mcp-server-github/) example MCP server.
+- Learn how to use a third-party OAuth provider, using the [GitHub](/agents/guides/remote-mcp-server/#add-authentication) example MCP server.

src/content/docs/agents/model-context-protocol/index.mdx

@@ -28,4 +28,4 @@ The MCP standard supports two modes of operation:
 
 ### Get Started
 
-Go to the [Getting Started](/agents/model-context-protocol/getting-started/) guide to learn how to build and deploy your first remote MCP server to Cloudflare.
+Go to the [Getting Started](/agents/guides/remote-mcp-server/) guide to learn how to build and deploy your first remote MCP server to Cloudflare.