feat(examples): rewrite multi-server example as minimal routing demo

Replace the full chatbot implementation with a minimal script that:
- Spawns two in-repo servers (server-quickstart + mcpServerOutputSchema)
- Connects a Client to each via StdioClientTransport
- Discovers tools and builds a prefixed routing table
- Calls one tool on each server to demonstrate routing

Removes the Anthropic SDK dependency and servers.json config file.
No API key required to run.

Co-Authored-By: Tadao <tadao@travisfixes.com>

Author: travisbreaks

examples/client-multi-server/README.md

@@ -1,82 +1,33 @@
-# Multi-Server MCP Client Example
+# Multi-Server Routing Example
 
-A CLI chatbot that connects to multiple MCP servers simultaneously, aggregates their tools, and routes tool calls to the correct server. This is the TypeScript equivalent of the [Python SDK's simple-chatbot example](https://github.com/modelcontextprotocol/python-sdk/tree/main/examples/clients/simple-chatbot).
+Minimal example showing how to connect to multiple MCP servers and route tool calls to the correct one.
 
-## Prerequisites
+Spawns two in-repo servers (`server-quickstart` and `mcpServerOutputSchema`), discovers their tools, builds a prefixed routing table, and calls one tool on each server to demonstrate the routing.
 
-- Node.js 20+
-- An [Anthropic API key](https://console.anthropic.com/)
+No API key required. No external config file needed.
 
 ## Quick Start
 
 ```bash
 # Install dependencies (from repo root)
 pnpm install
 
-# Set your API key
-export ANTHROPIC_API_KEY=your-api-key-here
-
-# Run with the default servers.json config
-cd examples/client-multi-server
-npx tsx src/index.ts
-```
-
-## Configuration
-
-Servers are configured via a JSON file (default: `servers.json` in the working directory). Pass a custom path as the first argument:
-
-```bash
-npx tsx src/index.ts /path/to/my-servers.json
-```
-
-The config file uses the same format as Claude Desktop and other MCP clients:
-
-```json
-{
-    "mcpServers": {
-        "everything": {
-            "command": "npx",
-            "args": ["-y", "@modelcontextprotocol/server-everything"]
-        },
-        "memory": {
-            "command": "npx",
-            "args": ["-y", "@modelcontextprotocol/server-memory"]
-        }
-    }
-}
+# Run the example
+npx tsx examples/client-multi-server/src/index.ts
 ```
 
-Each entry under `mcpServers` defines a server to connect to via stdio:
-
-- `command`: the executable to run
-- `args`: command-line arguments (optional)
-- `env`: additional environment variables (optional, merged with the current environment)
-
 ## How It Works
 
-1. Reads the server config and connects to each MCP server in sequence
-2. Discovers tools from every connected server and builds a unified tool list
-3. Maintains a mapping from each tool name to its originating server
-4. Sends the full tool list to Claude with each request
-5. When Claude calls a tool, routes the call to the correct server
-6. Supports multi-step tool use (agentic loop) where Claude can chain multiple tool calls
-
-## Usage
-
-```
-$ npx tsx src/index.ts
-Connecting to server: everything...
-  Connected to everything with tools: echo, add, ...
-
-Total tools available: 12
+1. Spawns each server as a child process via `StdioClientTransport`
+2. Connects a `Client` to each and calls `listTools()` to discover available tools
+3. Builds a routing map that prefixes each tool name with its server name (e.g. `weather-nws__get-alerts`) to avoid collisions
+4. Calls one tool on each server to prove routing works
+5. Cleans up all connections
 
-Multi-Server MCP Client Started!
-Type your queries or "quit" to exit.
+## Adapting This Pattern
 
-Query: What tools do you have access to?
+To route tool calls in your own multi-server setup:
 
-I have access to 12 tools from the "everything" server...
-
-Query: quit
-Disconnecting from everything...
-```
+- Prefix tool names with the server name when presenting them to an LLM
+- When the LLM calls a prefixed tool, strip the prefix and forward to the correct server
+- Check for collisions if multiple servers expose tools with the same name

examples/client-multi-server/package.json

@@ -3,15 +3,11 @@
     "private": true,
     "version": "2.0.0-alpha.0",
     "type": "module",
-    "bin": {
-        "mcp-multi-server-client": "./build/index.js"
-    },
     "scripts": {
         "build": "tsc",
         "typecheck": "tsc --noEmit"
     },
     "dependencies": {
-        "@anthropic-ai/sdk": "^0.74.0",
         "@modelcontextprotocol/client": "workspace:^"
     },
     "devDependencies": {