docs(examples): annotate runServerFromArgs / connectFromArgs at every call site

One comment line above each harness helper call so a reader landing on any
story file immediately sees what the helper abstracts and what they'd write
in their own server/client (serveStdio/createMcpHandler; new Client +
transport.connect). 14 server.ts call sites + 15 client.ts files. (#2325)

Author: felixweinberger

examples/caching/client.ts

@@ -12,6 +12,7 @@ interface Cacheable {
 }
 
 runClient('caching', async () => {
+    // connectFromArgs picks transport (default: spawn ./server.ts over stdio; --http <url>) and era (--legacy) from argv. Your code would construct a Client and connect over your chosen transport directly.
     const client = await connectFromArgs(import.meta.dirname);
     check.equal(client.getNegotiatedProtocolVersion(), '2026-07-28');
 

examples/caching/server.ts

@@ -49,4 +49,5 @@ function buildServer(): McpServer {
     return server;
 }
 
+// runServerFromArgs is the example harness's transport selector (default stdio, --http for HTTP). In your own server you'd call serveStdio(buildServer) or createMcpHandler(buildServer) directly.
 runServerFromArgs(buildServer);

examples/custom-methods/client.ts

@@ -16,6 +16,7 @@ runClient('custom-methods', async () => {
     // Custom methods carry no envelope semantics — connect as a plain 2025
     // client so the request reaches the server's setRequestHandler exactly as
     // a hand-wired stdio client would.
+    // connectFromArgs picks transport (default: spawn ./server.ts over stdio; --http <url>) and era (--legacy) from argv. Your code would construct a Client and connect over your chosen transport directly.
     const client = await connectFromArgs(import.meta.dirname, { versionNegotiation: undefined });
 
     const stages: string[] = [];

examples/custom-methods/server.ts

@@ -25,4 +25,5 @@ function buildServer(): McpServer {
     return mcp;
 }
 
+// runServerFromArgs is the example harness's transport selector (default stdio, --http for HTTP). In your own server you'd call serveStdio(buildServer) or createMcpHandler(buildServer) directly.
 runServerFromArgs(buildServer);

examples/custom-version/client.ts

@@ -7,6 +7,7 @@ import { check, connectFromArgs, runClient } from '../harness.js';
 runClient('custom-version', async () => {
     // A plain (2025-handshake) client; the server supports the SDK's stock
     // 2025 version so this negotiates that.
+    // connectFromArgs picks transport (default: spawn ./server.ts over stdio; --http <url>) and era (--legacy) from argv. Your code would construct a Client and connect over your chosen transport directly.
     const client = await connectFromArgs(import.meta.dirname, { versionNegotiation: undefined });
 
     // The server should advertise its supportedProtocolVersions in its

examples/custom-version/server.ts

@@ -23,4 +23,5 @@ function buildServer(): McpServer {
     return server;
 }
 
+// runServerFromArgs is the example harness's transport selector (default stdio, --http for HTTP). In your own server you'd call serveStdio(buildServer) or createMcpHandler(buildServer) directly.
 runServerFromArgs(buildServer);

examples/dual-era/client.ts

@@ -16,6 +16,7 @@ import { check, connectFromArgs, runClient } from '../harness.js';
 
 runClient('dual-era', async () => {
     // --- leg 1: plain 2025 client (initialize handshake) ---
+    // connectFromArgs picks transport (default: spawn ./server.ts over stdio; --http <url>) and era (--legacy) from argv. Your code would construct a Client and connect over your chosen transport directly.
     const legacy = await connectFromArgs(import.meta.dirname, { versionNegotiation: undefined });
     const legacyTools = await legacy.listTools();
     check.ok(legacyTools.tools.some(t => t.name === 'greet'));

examples/dual-era/server.ts

@@ -40,4 +40,5 @@ const buildServer = (ctx: McpRequestContext) => {
     return server;
 };
 
+// runServerFromArgs is the example harness's transport selector (default stdio, --http for HTTP). In your own server you'd call serveStdio(buildServer) or createMcpHandler(buildServer) directly.
 runServerFromArgs(buildServer);

examples/elicitation-form/client.ts

@@ -9,6 +9,7 @@ runClient('elicitation-form', async () => {
     // multi-round-trip `inputRequired` instead — see ../mrtr/). The harness
     // pins this story to the legacy era so `ctx.mcpReq.elicitInput` reaches
     // this handler.
+    // connectFromArgs picks transport (default: spawn ./server.ts over stdio; --http <url>) and era (--legacy) from argv. Your code would construct a Client and connect over your chosen transport directly.
     const client = await connectFromArgs(import.meta.dirname, { capabilities: { elicitation: { form: {} } } });
 
     let action: 'accept' | 'decline' = 'accept';

examples/elicitation-form/server.ts

@@ -37,4 +37,5 @@ function buildServer(): McpServer {
     return server;
 }
 
+// runServerFromArgs is the example harness's transport selector (default stdio, --http for HTTP). In your own server you'd call serveStdio(buildServer) or createMcpHandler(buildServer) directly.
 runServerFromArgs(buildServer);