chore: dedup InMemoryTransport export and normalize docs after rebase onto #1834

Author: felixweinberger

docs/migration-SKILL.md

@@ -440,15 +440,15 @@ const elicit = await ctx.mcpReq.send({ method: 'elicitation/create', params: { .
 const tool = await client.callTool({ name: 'my-tool', arguments: {} });
 ```
 
-| v1 call                                                      | v2 call                            |
-| ------------------------------------------------------------ | ---------------------------------- |
-| `client.request(req, ResultSchema)`                          | `client.request(req)`              |
-| `client.request(req, ResultSchema, options)`                 | `client.request(req, options)`     |
+| v1 call                                                                    | v2 call                                                      |
+| -------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| `client.request(req, ResultSchema)`                                        | `client.request(req)`                                        |
+| `client.request(req, ResultSchema, options)`                               | `client.request(req, options)`                               |
 | `client.experimental.tasks.callToolStream(params, ResultSchema, options?)` | `client.experimental.tasks.callToolStream(params, options?)` |
-| `ctx.mcpReq.send(req, ResultSchema)`                         | `ctx.mcpReq.send(req)`             |
-| `ctx.mcpReq.send(req, ResultSchema, options)`                | `ctx.mcpReq.send(req, options)`    |
-| `client.callTool(params, CompatibilityCallToolResultSchema)` | `client.callTool(params)`          |
-| `client.callTool(params, schema, options)`                   | `client.callTool(params, options)` |
+| `ctx.mcpReq.send(req, ResultSchema)`                                       | `ctx.mcpReq.send(req)`                                       |
+| `ctx.mcpReq.send(req, ResultSchema, options)`                              | `ctx.mcpReq.send(req, options)`                              |
+| `client.callTool(params, CompatibilityCallToolResultSchema)`               | `client.callTool(params)`                                    |
+| `client.callTool(params, schema, options)`                                 | `client.callTool(params, options)`                           |
 
 Remove unused schema imports: `CallToolResultSchema`, `CompatibilityCallToolResultSchema`, `ElicitResultSchema`, `CreateMessageResultSchema`, etc., when they were only used in `request()`/`send()`/`callTool()` calls.
 

docs/migration.md

@@ -139,7 +139,8 @@ app.all('/mcp', async (req, res) => {
 });
 ```
 
-With `sessionIdGenerator: undefined` the transport runs in stateless mode, so creating a fresh instance per request is correct. For stateful sessions, the transport must be created once per session and stored in a `Map<string, NodeStreamableHTTPServerTransport>` keyed by session ID — see `examples/server/src/simpleStreamableHttp.ts` for the full pattern.
+With `sessionIdGenerator: undefined` the transport runs in stateless mode, so creating a fresh instance per request is correct. For stateful sessions, the transport must be created once per session and stored in a `Map<string, NodeStreamableHTTPServerTransport>` keyed by session
+ID — see `examples/server/src/simpleStreamableHttp.ts` for the full pattern.
 
 ### `WebSocketClientTransport` removed
 
@@ -472,8 +473,8 @@ example.
 
 ### `Protocol.request()`, `ctx.mcpReq.send()`, and `Client.callTool()` no longer take a schema parameter
 
-The public `Protocol.request()`, `BaseContext.mcpReq.send()`, `Client.callTool()`, and `client.experimental.tasks.callToolStream()` methods no longer accept a Zod result schema argument. The SDK now resolves the correct result schema internally based on the method name. This means you no longer need to import result schemas
-like `CallToolResultSchema` or `ElicitResultSchema` when making requests.
+The public `Protocol.request()`, `BaseContext.mcpReq.send()`, `Client.callTool()`, and `client.experimental.tasks.callToolStream()` methods no longer accept a Zod result schema argument. The SDK now resolves the correct result schema internally based on the method name. This
+means you no longer need to import result schemas like `CallToolResultSchema` or `ElicitResultSchema` when making requests.
 
 **`client.request()` — Before (v1):**
 

packages/core/src/exports/public/index.ts

@@ -136,9 +136,6 @@ export type {
 export { isTerminal } from '../../experimental/tasks/interfaces.js';
 export { InMemoryTaskMessageQueue, InMemoryTaskStore } from '../../experimental/tasks/stores/inMemory.js';
 
-// Transport utilities
-export { InMemoryTransport } from '../../util/inMemory.js';
-
 // Validator types and classes
 export type { StandardSchemaWithJSON } from '../../util/standardSchema.js';
 export { AjvJsonSchemaValidator } from '../../validators/ajvProvider.js';