update authless example

ranbel · ranbel · commit 27b2e096cf5c · 2026-02-03T17:53:32.000-05:00
diff --git a/src/content/docs/agents/guides/remote-mcp-server.mdx b/src/content/docs/agents/guides/remote-mcp-server.mdx
@@ -9,100 +9,120 @@ sidebar:
 
 import { Details, Render, PackageManagers } from "~/components";
 
-## Deploy your first MCP server
-
 This guide will show you how to deploy your own remote MCP server on Cloudflare using [Streamable HTTP transport](/agents/model-context-protocol/transport/), the current MCP specification standard. You have two options:
 
 - **Without authentication** — anyone can connect and use the server (no login required).
 - **With [authentication and authorization](/agents/guides/remote-mcp-server/#add-authentication)** — users sign in before accessing tools, and you can control which tools an agent can call based on the user's permissions.
 
+## Deploy your first MCP server
+
 You can start by deploying a [public MCP server](https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-authless) without authentication, then add user authentication and scoped authorization later. If you already know your server will require authentication, you can skip ahead to the [next section](/agents/guides/remote-mcp-server/#add-authentication).
 
-The button below will guide you through everything you need to do to deploy this [example MCP server](https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-authless) to your Cloudflare account:
+### Deploy using a quickstart button
+
+The button below will guide you through everything you need to do to deploy an [example MCP server](https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-authless) to your Cloudflare account:
 
 [![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/mcp). 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 (for example, `remote-mcp-server-authless.your-account.workers.dev/mcp`). 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).
 
-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.
+If you are 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 clone this repository, [develop locally](/agents/guides/remote-mcp-server/#local-development), and start customizing the MCP server with your own [tools](/agents/model-context-protocol/tools/).
 
-### Set up and deploy your MCP server via CLI
+### Deploy using the CLI
 
-Alternatively, you can use the command line as shown below to create a new MCP Server on your local machine.
+You can use the [Wrangler CLI](/workers/wrangler) to create a new MCP Server on your local machine and deploy it to Cloudflare.
 
-<PackageManagers
-	type="create"
-	pkg="cloudflare@latest"
-	args={"my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless"}
-/>
+1. Open a terminal and run the following command:
 
-Now, you have the MCP server setup, with dependencies installed. Move into that project folder:
+	<PackageManagers
+		type="create"
+		pkg="cloudflare@latest"
+		args={"remote-mcp-server-authless --template=cloudflare/ai/demos/remote-mcp-authless"}
+	/>
 
-```sh
-cd my-mcp-server
-```
+	Now, you have the MCP server setup, with dependencies installed.
 
-#### Local development
+2. Move into the project folder:
 
-In the directory of your new project, run the following command to start the development server:
+	```sh
+	cd remote-mcp-server-authless
+	```
 
-```sh
-npm start
-```
+3. In the directory of your new project, run the following command to start the development server:
 
-Your MCP server is now running on `http://localhost:8788/mcp`.
+	```sh
+	npm start
+	```
 
-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.
+	```sh output
+	⎔ Starting local server...
+	[wrangler:info] Ready on http://localhost:8788
+	```
 
-```sh
-npx @modelcontextprotocol/inspector@latest
-```
+	Your MCP server is now running on `http://localhost:8788/mcp`.
 
-Open the MCP inspector in your web browser:
+4. To test the server locally:
+	1. 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.
 
-```sh
-open http://localhost:5173
-```
+		```sh
+		npx @modelcontextprotocol/inspector@latest
+		```
 
-In the inspector, enter the URL of your MCP server, `http://localhost:8788/mcp`, and click **Connect**. You should see the "List Tools" button, which will list the tools that your MCP server exposes.
+	2. Open the MCP inspector in your web browser:
 
-![MCP inspector — authenticated](~/assets/images/agents/mcp-inspector-authenticated.png)
+		```sh
+		open http://localhost:5173
+		```
 
-#### Deploy your MCP server
+	3. In the MCP inspector, enter the URL of your MCP server: `http://localhost:8788/mcp`, and select **Connect**. Select **List Tools** to show the tools that your MCP server exposes.
 
-You can deploy your MCP server to Cloudflare using the following [Wrangler CLI command](/workers/wrangler) within the example project:
+5. You can now deploy your MCP server to Cloudflare. From your project directory, run:
 
-```sh
-npx wrangler@latest deploy
-```
+	```sh
+	npx wrangler@latest deploy
+	```
 
-If you have already [connected a git repository](/workers/ci-cd/builds/) to the Worker with your MCP server, you can deploy your MCP server by pushing a change or merging a pull request to the main branch of the repository.
+	If you have already [connected a git repository](/workers/ci-cd/builds/) to the Worker with your MCP server, you can deploy your MCP server by pushing a change or merging a pull request to the main branch of the repository.
 
-After deploying, take the URL of your deployed MCP server, and enter it in the MCP inspector running on `http://localhost:5173`. You now have a remote MCP server, deployed to Cloudflare, that MCP clients can connect to.
+	The MCP server will be deployed to your `*.workers.dev` subdomain at `remote-mcp-server-authless.your-account.workers.dev/mcp`.
 
-### Connect your Remote MCP server to Claude and other MCP Clients via a local proxy
 
-Now that your MCP server is running, you can use the [`mcp-remote` local proxy](https://www.npmjs.com/package/mcp-remote) to connect Claude Desktop or other MCP clients to it — even though these tools aren't yet _remote_ MCP clients, and don't support remote transport or authorization on the client side. This lets you test what an interaction with your MCP server will be like with a real MCP client.
+6. To test the remote MCP server, take the URL of your deployed MCP server (`remote-mcp-server-authless.your-account.workers.dev/mcp`) and enter it in the MCP inspector running on `http://localhost:5173`.
 
-Update your Claude Desktop configuration to point to the URL of your MCP server. You can use either the `localhost:8788/mcp` URL, or the URL of your deployed MCP server:
+You now have a remote MCP server that MCP clients can connect to.
 
-```json
-{
-	"mcpServers": {
-		"math": {
-			"command": "npx",
-			"args": [
-				"mcp-remote",
-				"https://your-worker-name.your-account.workers.dev/mcp"
-			]
+### Connect from an MCP client via a local proxy
+
+Now that your remote MCP server is running, you can use the [`mcp-remote` local proxy](https://www.npmjs.com/package/mcp-remote) to connect Claude Desktop or other MCP clients to it — even if your MCP client does not support remote transport or authorization on the client side. This lets you test what an interaction with your remote MCP server will be like with a real MCP client.
+
+For example, to connect from Claude Desktop:
+
+1. Update your Claude Desktop configuration to point to the URL of your MCP server:
+
+	```json
+	{
+		"mcpServers": {
+			"math": {
+				"command": "npx",
+				"args": [
+					"mcp-remote",
+					"https://remote-mcp-server-authless.your-account.workers.dev/mcp"
+				]
+			}
 		}
 	}
-}
-```
+	```
+
+2. Restart Claude Desktop to load the MCP Server. Once this is done, Claude will be able to make calls to your remote MCP server.
+
+3. To test, ask Claude to use one of your tools. For example:
+	```txt
+	Could you use the math tool to add 23 and 19?
+	```
 
-Restart Claude Desktop after updating your config file to load the MCP Server. Once this is done, Claude will be able to make calls to your remote MCP server. You can test this by asking Claude to use one of your tools. For example: "Could you use the math tool to add 23 and 19?". Claude should invoke the tool and show the result generated by the MCP server.
+	Claude should invoke the tool and show the result generated by the remote MCP server.
 
-Learn more about other ways of using remote MCP servers with MCP clients here in [this section](/agents/guides/test-remote-mcp-server).
+To learn how to use remote MCP servers with other MCP clients, refer to [Test a Remote MCP Server](/agents/guides/test-remote-mcp-server).
 
 ## Add Authentication
 
diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/saas-mcp.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/saas-mcp.mdx
@@ -13,7 +13,7 @@ import {
 	GlossaryTooltip,
 	Tabs,
 	TabItem,
-	APIRequest,
+	APIRequest
 } from "~/components";
 
 You can secure [Model Context Protocol (MCP) servers](https://www.cloudflare.com/learning/ai/what-is-model-context-protocol-mcp/) by using Cloudflare Access as an OAuth Single Sign-On (SSO) provider.
