Fix broken links

Author: irvinebroque

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

@@ -37,7 +37,7 @@ Below we will run you through an example of building an MCP server that fetches
 Follow these steps to create and deploy your own MCP server on Cloudflare Workers.
 
 :::note
-Looking to deploy a MCP server that supports _remote_ connections over the Internet, with authentication and authorization? Check out our [guide](/docs/agents/model-context-protocol/getting-started) for building and deploying remote MCP servers to Cloudflare.
+Looking to deploy a MCP server that supports _remote_ connections over the Internet, with authentication and authorization? Check out our [guide](/agents/model-context-protocol/getting-started) for building and deploying remote MCP servers to Cloudflare.
 :::
 
 ### Create a new Worker

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

@@ -16,12 +16,12 @@ When building a [Model Context Protocol (MCP)](https://modelcontextprotocol.io)
 
 The Model Context Protocol uses [a subset of OAuth 2.1 for authorization](https://spec.modelcontextprotocol.io/specification/draft/basic/authorization/). OAuth allows your users to grant limited access to resources, without them having to share API keys or other credentials.
 
-Cloudflare provides an [OAuth Provider Library](https://github.com/cloudflare/ai/demos/remote-mcp-server/lib/workers-oauth-provider) that implements the provider side of the OAuth 2.1 protocol, allowing you to easily add authorization to your MCP server.
+Cloudflare provides an [OAuth Provider Library](https://github.com/cloudflare/workers-mcp/tree/next/vendor/workers-oauth-provider) that implements the provider side of the OAuth 2.1 protocol, allowing you to easily add authorization to your MCP server.
 
 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/model-context-protocol/examples/github/))
+2. **Integrate directly with a third-party OAuth provider**, such as GitHub or Google. ([Example](/cloudflare/ai/demos/remote-mcp-server-github/))
 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.
@@ -30,9 +30,9 @@ The following sections describe each of these options and link to runnable code
 
 ### (1) Your MCP Server handles authorization and authentication itself
 
-Your MCP Server, using the [OAuth Provider Library](https://github.com/cloudflare/ai/demos/remote-mcp-server/lib/workers-oauth-provider), can handle the complete OAuth authorization flow, without any third-party involvement.
+Your MCP Server, using the [OAuth Provider Library](https://github.com/cloudflare/workers-mcp/tree/next/vendor/workers-oauth-provider), can handle the complete OAuth authorization flow, without any third-party involvement.
 
-The [Workers OAuth Provider Library](https://github.com/cloudflare/ai/demos/remote-mcp-server/lib/workers-oauth-provider) is a Cloudflare Worker that implements a [`fetch()` handler](/workers/runtime-apis/handlers/fetch/), and handles incoming requests to your MCP server.
+The [Workers OAuth Provider Library](https://github.com/cloudflare/workers-mcp/tree/next/vendor/workers-oauth-provider) is a Cloudflare Worker that implements a [`fetch()` handler](/workers/runtime-apis/handlers/fetch/), and handles incoming requests to your MCP server.
 
 You provide your own handlers for your MCP Server's API, and autentication and authorization logic, and URI paths for the OAuth endpoints, as shown below:
 
@@ -77,7 +77,7 @@ Remember — [authentication is different from authorization](https://www.cloud
 
 ### (2) Third-party OAuth Provider
 
-The [OAuth Provider Library](https://github.com/cloudflare/ai/demos/remote-mcp-server/lib/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-mcp/tree/next/vendor/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).
 
 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.
 
@@ -120,13 +120,13 @@ sequenceDiagram
     M->>C: MCP access token
 ```
 
-Read the docs for the [Workers oAuth Provider Library](https://github.com/cloudflare/ai/demos/remote-mcp-server/lib/workers-oauth-provider) for more details.
+Read the docs for the [Workers oAuth Provider Library](https://github.com/cloudflare/workers-mcp/tree/next/vendor/workers-oauth-provider) for more details.
 
 ### (3) Bring your own OAuth Provider
 
 If your application already implements an Oauth Provider itself, or you use Stytch, Auth0, or authorization-as-a-service provider, you can use this in the same way that you would use a third-party OAuth provider, described above in (2).
 
 ## Next steps
 
-- [Learn how to use the OAuth Provider SDK](/agents/model-context-protocol/authorization/oauth-provider-api-reference/)
-- Learn how to use a third-party OAuth provider, using the [GitHub](/agents/model-context-protocol/examples/github/) and [Slack](/agents/model-context-protocol/examples/slack/) examples.
+- [Learn how to use the Workers OAuth Provider Library](https://github.com/cloudflare/workers-mcp/tree/next/vendor/workers-oauth-provider)
+- Learn how to use a third-party OAuth provider, using the [GitHub](/agents/guides/remote-mcp-server-github/) and [Slack](/agents/guides/remote-mcp-server-slack/) examples.

src/content/docs/agents/model-context-protocol/getting-started.mdx

@@ -230,4 +230,4 @@ You should now be able to connect to your MCP server using the MCP inspector, an
 
 - Add [tools](/agents/model-context-protocol/tools/) to your MCP server.
 - Customize your MCP Server's [authentication and authorization](/agents/model-context-protocol/authorization/).
-- Try other [example MCP servers](/agents/model-context-protocol/examples/)
+- Try our the [Slack MCP server](/agents/guides/remote-mcp-server-slack/) for another example of a remote MCP server.