@orkestrel/mcp 0.0.27 → 0.0.29

package/README.md

@@ -1,15 +1,12 @@
 # @orkestrel/mcp
 
-A typed [Model Context Protocol](https://modelcontextprotocol.io) client/server
-for the `@orkestrel` line, bridging the `@orkestrel/tool` registry to MCP with
-pluggable HTTP, WebSocket, and stdio transports. `createMCPServer` exposes a
-live `ToolManagerInterface`; `createMCPClient` drives a remote MCP server and
-surfaces its tools as local `ToolInterface`s. No agent runtime is required.
-The dispatch core is transport- and provider-agnostic
-(`src/core` — JSON-RPC 2.0, no HTTP, no `as`); every transport (Streamable
-HTTP over `@orkestrel/router` / `@orkestrel/server`, WebSocket over
-`@orkestrel/websocket`, and stdio over `@orkestrel/process`) lives one layer
-out (`src/server`), each mechanism, not policy. Part of the `@orkestrel` line.
+> The Model Context Protocol layer: a typed JSON-RPC 2.0 client/server pair with pluggable
+> HTTP, WebSocket, stdio, and browser transports.
+
+Bridge the `@orkestrel/tool` registry to MCP: `createMCPServer` exposes a live
+`ToolManagerInterface` to any MCP client, and `createMCPClient` drives a remote MCP server
+and surfaces its tools as local `ToolInterface`s. No agent runtime is required. Part of the
+`@orkestrel` line.
 
 ## Install
 
@@ -30,8 +27,6 @@ npm install @orkestrel/mcp
 
 ## Usage
 
-Expose a tool registry over MCP, mounted on the HTTP spine:
-
 ```ts
 import { createMCPLegacy, createMCPServer } from '@orkestrel/mcp'
 import { createMCPRoutes } from '@orkestrel/mcp/server'
@@ -46,6 +41,8 @@ const routes = createMCPRoutes(createMCPLegacy(mcp)) // answers `initialize` too
 router.add(routes)
 ```
 
+This example exposes a tool registry over MCP, mounted on the HTTP spine.
+
 Drive a remote MCP server as a client, over the same transport-agnostic core:
 
 ```ts
@@ -57,10 +54,10 @@ const client = createMCPClient({
 })
 await client.connect()
 const tools = await client.tools()
-const value = await client.call('add', { x: 2, y: 5 })
+const outcome = await client.call('add', { x: 2, y: 5 })
 ```
 
-The SAME `MCPClient` drives a `createWebSocketClientTransport` or
+The same `MCPClient` drives a `createWebSocketClientTransport` or
 `createStdioClientTransport` instead — only the injected transport changes.
 
 ## Guide
@@ -96,7 +93,7 @@ The publication facts, each with its number. Full detail, plus every
 protocol-level gap and non-goal, is in
 [the MCP guide](https://github.com/orkestrel/mcp/blob/main/guides/mcp.md#declared-packaging-limits).
 
-- **No IDE evidence.** See above. The conformance number is about the wire
+- **No IDE evidence.** See the [wire conformance evidence](https://github.com/orkestrel/mcp#proven). The conformance number is about the wire
   and does not transfer to a host application.
 - **No top-level `types` field.** Every `exports` subpath carries a `types`
   condition, so `node16`, `nodenext`, and `bundler` resolution find