@mcp-b/webmcp-ts-sdk 2.1.0 → 2.2.1

package/README.md

@@ -14,13 +14,13 @@
 
 ## Why Use @mcp-b/webmcp-ts-sdk?
 
-| Feature | Benefit |
-|---------|---------|
+| Feature                       | Benefit                                                               |
+| ----------------------------- | --------------------------------------------------------------------- |
 | **Dynamic Tool Registration** | Register tools after transport connection - required for browser apps |
-| **Minimal Overhead** | Only ~50 lines of custom code on top of official SDK |
-| **Full SDK Compatibility** | Re-exports all types, classes, and utilities from official SDK |
-| **Type-Safe** | No prototype hacks - clean TypeScript extension |
-| **Auto-Updates** | Types and protocol follow official SDK automatically |
+| **Minimal Overhead**          | Only ~50 lines of custom code on top of official SDK                  |
+| **Full SDK Compatibility**    | Re-exports all types, classes, and utilities from official SDK        |
+| **Type-Safe**                 | No prototype hacks - clean TypeScript extension                       |
+| **Auto-Updates**              | Types and protocol follow official SDK automatically                  |
 
 ## Overview
 
@@ -41,12 +41,19 @@ public registerCapabilities(capabilities: ServerCapabilities): void {
 
 For the Web Model Context API, this restriction is incompatible because:
 
-1. **Tools arrive dynamically** - Web pages call `window.navigator.modelContext.provideContext({ tools: [...] })` at any time
+1. **Tools arrive dynamically** - Web pages call `window.navigator.modelContext.registerTool(...)` at any time
 2. **Transport must be ready immediately** - The MCP server/transport needs to be connected when the page loads
 3. **Asynchronous registration** - Tools are registered as the page's JavaScript executes, potentially long after initialization
 
 This package solves the problem by **pre-registering tool capabilities** before the transport connects, allowing dynamic tool registration to work seamlessly.
 
+Compatibility note:
+
+- `BrowserMcpServer.registerTool(tool, options?)` accepts the WebMCP April 23, 2026 draft signature, including `options.signal` (`AbortSignal`) for unregistration. When the signal aborts, both the server-side registration and the mirrored native registration are removed.
+- The same call still returns a deprecated `{ unregister }` compatibility handle so existing MCP-B integrations do not break, even though spec/native runtimes return `undefined`. The handle will be removed in the next major version — prefer `options.signal`.
+- `unregisterTool(name)` was removed from the WebMCP draft on April 23, 2026 in favor of the `AbortSignal` flow. It is kept on `BrowserMcpServer` with a one-time deprecation warning to interoperate with current Chrome Beta 147 (which still ships the string-name API). It will be removed in the next major version.
+- `provideContext()` and `clearContext()` were removed from the WebMCP draft on March 5, 2026. They are kept here as deprecated compatibility shims and emit a one-time deprecation warning when invoked.
+
 ## Modifications from Official SDK
 
 ### BrowserMcpServer Class
@@ -60,8 +67,8 @@ export class BrowserMcpServer extends BaseMcpServer {
     const enhancedOptions = {
       ...options,
       capabilities: mergeCapabilities(options?.capabilities || {}, {
-        tools: { listChanged: true }
-      })
+        tools: { listChanged: true },
+      }),
     };
     super(serverInfo, enhancedOptions);
   }
@@ -81,16 +88,19 @@ export class BrowserMcpServer extends BaseMcpServer {
 This package re-exports almost everything from the official SDK:
 
 ### Types
+
 - All MCP protocol types (`Tool`, `Resource`, `Prompt`, etc.)
 - Request/response schemas
 - Client and server capabilities
 - Error codes and constants
 
 ### Classes
+
 - `Server` - Base server class (unchanged)
 - `McpServer` - Aliased to `BrowserMcpServer` with our modifications
 
 ### Utilities
+
 - `Transport` interface
 - `mergeCapabilities` helper
 - Protocol version constants
@@ -113,7 +123,7 @@ import { TabServerTransport } from '@mcp-b/transports';
 
 const server = new McpServer({
   name: 'my-web-app',
-  version: '1.0.0'
+  version: '1.0.0',
 });
 
 // Connect transport first
@@ -121,42 +131,50 @@ const transport = new TabServerTransport({ allowedOrigins: ['*'] });
 await server.connect(transport);
 
 // Now you can register tools dynamically (this would fail with official SDK)
-server.registerTool('my-tool', {
-  description: 'A dynamically registered tool',
-  inputSchema: { message: z.string() },
-  // Output schemas enable structured, type-safe AI responses
-  outputSchema: { result: z.string() }
-}, async ({ message }) => {
-  return {
-    content: [{ type: 'text', text: `Echo: ${message}` }],
-    // structuredContent must match the outputSchema
-    structuredContent: { result: `Echo: ${message}` }
-  };
-});
+server.registerTool(
+  'my-tool',
+  {
+    description: 'A dynamically registered tool',
+    inputSchema: { message: z.string() },
+    // Output schemas enable structured, type-safe AI responses
+    outputSchema: { result: z.string() },
+  },
+  async ({ message }) => {
+    return {
+      content: [{ type: 'text', text: `Echo: ${message}` }],
+      // structuredContent must match the outputSchema
+      structuredContent: { result: `Echo: ${message}` },
+    };
+  }
+);
 
 // Example with complex output schema
-server.registerTool('analyze-data', {
-  description: 'Analyze data and return structured results',
-  inputSchema: {
-    data: z.array(z.number()),
-    operation: z.enum(['sum', 'average', 'stats'])
+server.registerTool(
+  'analyze-data',
+  {
+    description: 'Analyze data and return structured results',
+    inputSchema: {
+      data: z.array(z.number()),
+      operation: z.enum(['sum', 'average', 'stats']),
+    },
+    outputSchema: {
+      result: z.number(),
+      operation: z.string(),
+      metadata: z.object({
+        count: z.number(),
+        min: z.number().optional(),
+        max: z.number().optional(),
+      }),
+    },
   },
-  outputSchema: {
-    result: z.number(),
-    operation: z.string(),
-    metadata: z.object({
-      count: z.number(),
-      min: z.number().optional(),
-      max: z.number().optional()
-    })
+  async ({ data, operation }) => {
+    const stats = calculateStats(data, operation);
+    return {
+      content: [{ type: 'text', text: `Result: ${stats.result}` }],
+      structuredContent: stats,
+    };
   }
-}, async ({ data, operation }) => {
-  const stats = calculateStats(data, operation);
-  return {
-    content: [{ type: 'text', text: `Result: ${stats.result}` }],
-    structuredContent: stats
-  };
-});
+);
 ```
 
 ## Architecture