Update MCP server documentation based on PR feedback

Author: dinasaur404

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

@@ -5,34 +5,69 @@ sidebar:
   order: 100
   group:
     hideIndex: true
-description: Build and deploy an MCP server on Cloudflare Workers
+description: Learn how to create, deploy, and configure an MCP server on Cloudflare Workers to enable AI assistants to interact with your services directly.
 ---
 
 import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 import { Aside } from '@astrojs/starlight/components';
 
-[Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) is an open standard that allows AI assistants & LLMs to interact with services directly. If you want users to access your service or product straight from their AI assistant, you can enable this by spinning up an MCP server for your application. 
+In this guide, you will learn how to build and deploy a Model Context Protocol (MCP) server on Cloudflare Workers.
 
-## Building an MCP Server on Cloudflare Workers
+[Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) is an open standard that allows AI agents and assistants (like [Claude Desktop](https://claude.ai/download), [Cursor](https://www.cursor.com/), or [Anthropic's Claude](https://www.anthropic.com/claude)) to interact with services directly. If you want users to access your service through an AI agent, you can spin up an MCP server for your application.
 
-Normally, setting up an MCP server requires writing boilerplate code to handle routing, define types, and standing up a server that implements the MCP protocol. But with [Cloudflare Workers](/workers/), all the heavy lifting is done for you, so all you need to do is define your service's functionality as TypeScript methods on your Worker
-Once deployed, your Worker becomes an MCP server that AI assistants (as long as they support MCP) can connect to and use to interact with your service.
+### Why use Cloudflare Workers for MCP?
 
-<Aside type="caution">
-Remote MCP servers are not supported yet. The workers-mcp tooling creates a local proxy that forwards requests to your Worker, allowing the server to be used by an MCP client.
-</Aside>
+With Cloudflare Workers and the [workers-mcp](https://github.com/cloudflare/workers-mcp/) package, you can turn any API or service into an MCP server with minimal setup. Just define your API methods as TypeScript functions, and workers-mcp takes care of tool discovery, protocol handling, and request routing. Once deployed, MCP clients like Claude can connect and interact with your service automatically.
+
+#### Example: Exposing a Weather API as an MCP server
 
-## Benefits
+Here's a Cloudflare Worker that fetches weather data from an external API and exposes it as an MCP tool that Claude can call directly:
+
+```ts
+import { WorkerEntrypoint } from 'cloudflare:workers';
+import { ProxyToSelf } from 'workers-mcp';
 
-- **Minimal setup & built-in boilerplate:** The Worker automatically handles API routing, server management, and MCP protocol compliance. The [workers-mcp](https://www.npmjs.com/package/workers-mcp) package bootstraps your MCP server, allowing you to focus on your service logic.
-- **Automatic documentation:** Public methods annotated with JSDoc are automatically documented and exposed as MCP tools. This means AI assistants can quickly understand how to interact with your service, making tool discovery and integration much easier.
-- **Scalability & performance:** Deploy your MCP server on Cloudflare's global edge network so that users can make fast, performant requests from their LLMs. Cloudflare will handle traffic spikes and high load, ensuring your service remains available and responsive.
-- **Expand MCP server capabilities:** Easily connect to Workers AI, D1, Durable Objects, and other Cloudflare services to add more functionality to your MCP Server. 
+export default class WeatherWorker extends WorkerEntrypoint<Env> {
+  /**
+   * Get current weather for a location
+   * @param location {string} City name or zip code
+   * @return {object} Weather information
+   */
+  async getWeather(location: string) {
+    // Connect to a weather API
+    const response = await fetch(`https://api.weather.example/v1/${location}`);
+    const data = await response.json();
+    return {
+      temperature: data.temp,
+      conditions: data.conditions,
+      forecast: data.forecast
+    };
+  }
+
+  /**
+   * @ignore
+   */
+  async fetch(request: Request): Promise<Response> {
+    // ProxyToSelf handles MCP protocol compliance
+    return new ProxyToSelf(this).fetch(request);
+  }
+}
+```
+
+**How it works:**
+* **TypeScript methods as MCP tools:** Each public method in your class is exposed as an MCP tool that agents can call. In this example, getWeather is the tool that fetches data from an external weather API.
+* **Automatic tool documentation:** JSDoc comments define the tool description, parameters, and return values, so Claude knows exactly how to call your method and interpret the response.
+* **Build-in MCP compatibility:** The `ProxyToSelf` class handles all MCP protocol requirements
+* **Enforced type safety:** Parameter and return types are automatically derived from your TypeScript definitions
 
 ## Get Started
 
 Follow these steps to create and deploy your own MCP server on Cloudflare Workers.
 
+<Aside type="note">
+Remote MCP servers are not supported yet. The workers-mcp tooling creates a local proxy that forwards requests to your Worker, allowing the server to be used by an MCP client.
+</Aside>
+
 
 ### Create a new Worker 
 
@@ -97,7 +132,7 @@ export default class MyWorker extends WorkerEntrypoint<Env> {
 }
 ```
 
-This converts your Cloudflare Worker into an MCP server, enabling interactions with AI assistants. The key components are:
+This converts your Cloudflare Worker into an MCP server, enabling interactions with AI assistants. **The key components are:**
 - **WorkerEntrypoint:** The WorkerEntrypoint class handles all incoming request management and routing. This provides the structure needed to expose MCP tools within the Worker.
 - **Tool Definition:** Methods, for example, sayHello, are annotated with JSDoc, which automatically registers the method as an MCP tool. AI assistants can call this method dynamically, passing a name and receiving a greeting in response. Additional tools can be defined using the same pattern.
 - **ProxyToSelf:** MCP servers must follow a specific request/response format. ProxyToSelf ensures that incoming requests are properly routed to the correct MCP tools. Without this, you would need to manually parse requests and validate responses.
@@ -121,10 +156,10 @@ npm run deploy
 ```
 **Note:** If you change method names, parameters, or add/remove methods, Claude and other MCP clients will not see these updates until you restart them. This is because MCP clients cache the tool metadata for performance reasons.
 ### Connecting MCP clients to your server
-The workers-mcp setup command automatically configures Claude Desktop to work with your MCP server. To use your MCP server through other [MCP clients](https://modelcontextprotocol.io/clients), you'll need to configure them manually.
+The `workers-mcp setup` command automatically configures Claude Desktop to work with your MCP server. To use your MCP server through other [MCP clients](https://modelcontextprotocol.io/clients), you'll need to configure them manually.
 
 #### Cursor
-To get your Cloudflare MCP server working in Cursor, you need to combine the 'command' and 'args' from your config file into a single string and use type 'command'.
+To get your Cloudflare MCP server working in [Cursor](https://modelcontextprotocol.io/clients#cursor), you need to combine the 'command' and 'args' from your config file into a single string and use type 'command'.
 
 In Cursor, create an MCP server entry with:
 
@@ -137,7 +172,7 @@ For example, using the same configuration as above, your Cursor command would be
 ```
 
 #### Other MCP clients
-For Windsurf and other MCP clients, update your configuration file to include your worker using the same format as Claude Desktop:
+For [Windsurf](https://modelcontextprotocol.io/clients#windsurf-editor) and other [MCP clients](https://modelcontextprotocol.io/clients#client-details), update your configuration file to include your worker using the same format as Claude Desktop:
 ```json
 {
   "mcpServers": {