diff --git a/src/content/docs/agents/guides/remote-mcp-server.mdx b/src/content/docs/agents/guides/remote-mcp-server.mdx index 2dc474c8bd56467..fbc889892dfcfa7 100644 --- a/src/content/docs/agents/guides/remote-mcp-server.mdx +++ b/src/content/docs/agents/guides/remote-mcp-server.mdx @@ -20,7 +20,7 @@ The button below will guide you through everything you need to do to deploy this [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-authless) -Once deployed, this server will be live at your workers.dev subdomain (e.g. remote-mcp-server-authless.your-account.workers.dev/sse). You can connect to it immediately using the [AI Playground](https://playground.ai.cloudflare.com/) (a remote MCP client), [MCP inspector](https://github.com/modelcontextprotocol/inspector) or [other MCP clients](/agents/guides/remote-mcp-server/#connect-your-remote-mcp-server-to-claude-and-other-mcp-clients-via-a-local-proxy). Then, once you're ready, you can customize the MCP server and add your own [tools](/agents/model-context-protocol/tools/). +Once deployed, this server will be live at your workers.dev subdomain (e.g. remote-mcp-server-authless.your-account.workers.dev/sse). You can connect to it immediately using the [AI Playground](https://playground.ai.cloudflare.com/) (a remote MCP client), [MCP inspector](https://github.com/modelcontextprotocol/inspector) or [other MCP clients](/agents/guides/remote-mcp-server/#connect-your-remote-mcp-server-to-claude-and-other-mcp-clients-via-a-local-proxy). Then, once you're ready, you can customize the MCP server and add your own [tools](/agents/model-context-protocol/tools/). If you're using the "Deploy to Cloudflare" button, a new git repository will be set up on your GitHub or GitLab account for your MCP server, configured to automatically deploy to 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. @@ -48,7 +48,7 @@ In the directory of your new project, run the following command to start the dev npm start ``` -Your MCP server is now running on `http://localhost:8787/sse`. +Your MCP server is now running on `http://localhost:8788/sse`. In a new terminal, run the [MCP inspector](https://github.com/modelcontextprotocol/inspector). The MCP inspector is an interactive MCP client that allows you to connect to your MCP server and invoke tools from a web browser. @@ -62,7 +62,7 @@ Open the MCP inspector in your web browser: open http://localhost:5173 ``` -In the inspector, enter the URL of your MCP server, `http://localhost:8787/sse`, and click **Connect**. You should see the "List Tools" button, which will list the tools that your MCP server exposes. +In the inspector, enter the URL of your MCP server, `http://localhost:8788/sse`, and click **Connect**. You should see the "List Tools" button, which will list the tools that your MCP server exposes. ![MCP inspector — authenticated](~/assets/images/agents/mcp-inspector-authenticated.png) @@ -182,7 +182,7 @@ Run the following command to start the development server: npm start ``` -Your MCP server is now running on `http://localhost:8787/sse`. +Your MCP server is now running on `http://localhost:8788/sse`. In a new terminal, run the [MCP inspector](https://github.com/modelcontextprotocol/inspector). The MCP inspector is an interactive MCP client that allows you to connect to your MCP server and invoke tools from a web browser. @@ -196,7 +196,7 @@ Open the MCP inspector in your web browser: open http://localhost:5173 ``` -In the inspector, enter the URL of your MCP server, `http://localhost:8787/sse`, and click **Connect**: +In the inspector, enter the URL of your MCP server, `http://localhost:8788/sse`, and click **Connect**: You should be redirected to a GitHub login or authorization page. After authorizing the MCP Client (the inspector) access to your GitHub account, you will be redirected back to the inspector. You should see the "List Tools" button, which will list the tools that your MCP server exposes. diff --git a/src/content/docs/agents/guides/test-remote-mcp-server.mdx b/src/content/docs/agents/guides/test-remote-mcp-server.mdx index 5a5c8e07e12eb46..3e0b1d425125931 100644 --- a/src/content/docs/agents/guides/test-remote-mcp-server.mdx +++ b/src/content/docs/agents/guides/test-remote-mcp-server.mdx @@ -47,7 +47,7 @@ Even though [Claude Desktop](https://claude.ai/download) doesn't yet support rem } ``` -This tells Claude to communicate with your MCP server running at `http://localhost:8787/sse`. +This tells Claude to communicate with your MCP server running at `http://localhost:8788/sse`. 3. Save the file and restart Claude Desktop (command/ctrl + R). When Claude restarts, a browser window will open showing your OAuth login page. Complete the authorization flow to grant Claude access to your MCP server.