You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/agents/guides/remote-mcp-server.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ The button below will guide you through everything you need to do to deploy this
22
22
23
23
[](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-authless)
24
24
25
-
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/).
25
+
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/).
26
26
27
27
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.
28
28
@@ -50,7 +50,7 @@ In the directory of your new project, run the following command to start the dev
50
50
npm start
51
51
```
52
52
53
-
Your MCP server is now running on `http://localhost:8787/sse`.
53
+
Your MCP server is now running on `http://localhost:8788/sse`.
54
54
55
55
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.
56
56
@@ -64,7 +64,7 @@ Open the MCP inspector in your web browser:
64
64
open http://localhost:5173
65
65
```
66
66
67
-
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.
67
+
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.
@@ -184,7 +184,7 @@ Run the following command to start the development server:
184
184
npm start
185
185
```
186
186
187
-
Your MCP server is now running on `http://localhost:8787/sse`.
187
+
Your MCP server is now running on `http://localhost:8788/sse`.
188
188
189
189
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.
190
190
@@ -198,7 +198,7 @@ Open the MCP inspector in your web browser:
198
198
open http://localhost:5173
199
199
```
200
200
201
-
In the inspector, enter the URL of your MCP server, `http://localhost:8787/sse`, and click **Connect**:
201
+
In the inspector, enter the URL of your MCP server, `http://localhost:8788/sse`, and click **Connect**:
202
202
203
203
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.
Copy file name to clipboardExpand all lines: src/content/docs/agents/guides/test-remote-mcp-server.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ Even though [Claude Desktop](https://claude.ai/download) doesn't yet support rem
49
49
}
50
50
```
51
51
52
-
This tells Claude to communicate with your MCP server running at `http://localhost:8787/sse`.
52
+
This tells Claude to communicate with your MCP server running at `http://localhost:8788/sse`.
53
53
54
54
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.
0 commit comments