@wakeshift/sdk 0.7.1 → 0.7.2

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 What changed in each release of `@wakeshift/sdk`. 0.4.0 is the first published release: to start with it, read the [README](README.md). Its notes below, and the earlier releases', are for apps that ran the preview builds.
 
+## 0.7.2 (2026-11-02)
+
+### Fixed
+
+- **`@modelcontextprotocol/server` 2.3.0 or later.** The peer dependency was `^2.0.0`, but on 2.0, 2.1 and 2.2 Claude Code's `wakeshift_wait` never completes: those releases answer `tasks/get` and `tasks/cancel` on protocol 2026-07-28 with "Method not found" themselves, before `attach` sees them ([modelcontextprotocol/typescript-sdk#2598](https://github.com/modelcontextprotocol/typescript-sdk/issues/2598), fixed in 2.3.0 by [#2599](https://github.com/modelcontextprotocol/typescript-sdk/pull/2599)). So conversations told to use the wait tool weren't woken. Everything else (wrapped tools, the built-in tools, MCP Events with `events/poll` and webhooks) works on 2.0 and later. The peer range is now `^2.3.0`: upgrade with `npm install @modelcontextprotocol/server@^2.3.0`. `@modelcontextprotocol/sdk` 1.x is unaffected.
+- **`attach` warns on an older 2.x.** Given a server from `@modelcontextprotocol/server` before 2.3.0, `attach` warns once (through `onWarning`), naming the version to upgrade to.
+
 ## 0.7.1 (2026-11-01)
 
 ### Fixed

package/README.md

@@ -2,7 +2,7 @@
 
 Let agents subscribe to things in your app. You define the events your app offers, serve them on your MCP server, and emit them when they happen; Wakeshift wakes every subscribed agent, whether it's Claude Code, Codex, ChatGPT or another. Your events follow MCP Events: clients that speak it subscribe natively, and Wakeshift bridges every other agent. You don't deal with harnesses.
 
-Node 22 or later. The package is ESM-only: load it with `import`, from an ES module (`"type": "module"`, or a `.mjs` or `.mts` file). It has no CommonJS build, so `require("@wakeshift/sdk")` works only where Node can require ES modules. It works with either MCP TypeScript SDK: `@modelcontextprotocol/server` 2.x (2.0 or later), which this page uses, or `@modelcontextprotocol/sdk` 1.x (1.23 or later: the first that takes zod 4; [below](#using-modelcontextprotocolsdk-1x)). Its peer dependencies are the one you use and `zod`: 4.2 or later with 2.x, 3.25 or later with 1.x. Import `z` from `"zod"`, not `"zod/v4"`: the SDK's schemas are built from `"zod"`, and the MCP SDK refuses a schema that mixes the two.
+Node 22 or later. The package is ESM-only: load it with `import`, from an ES module (`"type": "module"`, or a `.mjs` or `.mts` file). It has no CommonJS build, so `require("@wakeshift/sdk")` works only where Node can require ES modules. It works with either MCP TypeScript SDK: `@modelcontextprotocol/server` 2.x (2.3 or later), which this page uses, or `@modelcontextprotocol/sdk` 1.x (1.23 or later: the first that takes zod 4; [below](#using-modelcontextprotocolsdk-1x)). Its peer dependencies are the one you use and `zod`: 4.2 or later with 2.x, 3.25 or later with 1.x. Import `z` from `"zod"`, not `"zod/v4"`: the SDK's schemas are built from `"zod"`, and the MCP SDK refuses a schema that mixes the two.
 
 ## Install
 
@@ -348,6 +348,8 @@ npm run test:v2   # the same unit tests on @modelcontextprotocol/server 2.x
 npm run build     # dist/
 ```
 
+`sh scripts/mcp-floor.sh` installs the oldest `@modelcontextprotocol/server` the peer range allows (unsaved), for running `npm run test:v2` on it; `npm ci` puts the locked versions back.
+
 The end-to-end tests (`test/e2e*.test.ts`) run against a Wakeshift server, so they run in Wakeshift's own repository and skip here.
 
 ## Contributing and security

package/dist/host.js

@@ -15,7 +15,10 @@
 //     and a params schema on 2.x;
 //   - tasks/get and tasks/cancel: 2.x answers them on protocol 2026-07-28
 //     only for a handler registered with a params schema (the tasks
-//     extension's methods), so setTaskMethod registers them that way;
+//     extension's methods), so setTaskMethod registers them that way.
+//     Before 2.3.0 it refused them there whatever was registered
+//     (modelcontextprotocol/typescript-sdk#2598, fixed by #2599), so the
+//     peer range starts at 2.3.0 and routesTasks tells attach to warn;
 //   - protocol 2026-07-28: 1.x doesn't speak it, so discover.ts teaches it;
 //     2.x speaks it itself (server/discover, resultType, ttlMs and
 //     cacheScope).
@@ -29,6 +32,12 @@ import { z } from "zod";
 import * as z4 from "zod/v4";
 import { normalizeObjectSchema, safeParseAsync } from "./zod.js";
 const VERSION_META = "io.modelcontextprotocol/protocolVersion";
+/**
+ * @internal The oldest @modelcontextprotocol/server that serves tasks/get
+ * and tasks/cancel on protocol 2026-07-28 (modelcontextprotocol/typescript-sdk#2599):
+ * the floor of the SDK's peer range for it.
+ */
+export const TASKS_MIN_SERVER = "2.3.0";
 function lowOf(server) {
     return server.server;
 }
@@ -210,6 +219,9 @@ class V1Host extends BaseHost {
         // setRequestHandler would ask for its own tasks capability, an older
         // revision's, never advertised.)
     }
+    routesTasks() {
+        return true;
+    }
     async validOutput(outputSchema, result) {
         // McpServer 1.x's validateToolOutput: an object schema, and structured content that parses.
         if (!outputSchema)
@@ -243,6 +255,15 @@ class V2Host extends BaseHost {
             throw Object.assign(new Error("Method not found"), { code: -32601 });
         });
     }
+    routesTasks() {
+        // 2.3.0's fix keeps the methods registered with a schema in this set,
+        // and lets them past the era gate; 2.0 to 2.2 have no such set. 2.x
+        // doesn't expose its version (nor its package.json), so the fix is
+        // what's checked, private like _requestHandlers. A release that renames
+        // it would only warn wrongly, and fails v2.test.ts's check that the
+        // installed 2.x doesn't warn, on the Dependabot bump that brings it.
+        return this.low._customSchemaRequestMethods instanceof Set;
+    }
     async validOutput(outputSchema, result) {
         // McpServer 2.x's validateToolOutput: structured content (any JSON
         // value) that the output schema (a Standard Schema) accepts.
@@ -362,6 +383,7 @@ export function toolsOnlyHost(opts) {
         },
         setMethod: noop,
         setTaskMethod: noop,
+        routesTasks: () => true,
         handlers: () => null,
         clientName: () => undefined,
         clientCapabilities: () => undefined,

package/dist/tasks.js

@@ -16,6 +16,7 @@
 // zero-install path (Claude Code's Monitor). Everything else is unchanged.
 import { WakeshiftError } from "./errors.js";
 import { TASKS_EXTENSION, takesTasks } from "./discover.js";
+import { TASKS_MIN_SERVER } from "./host.js";
 import { RpcError } from "./mcp.js";
 import { WAKE_ARG_DESCRIPTIONS } from "./toolcall.js";
 import { toolCallOf } from "./wakeshift.js";
@@ -52,6 +53,9 @@ export function serveTasks(wake, host, callerOf) {
     const handlers = host.handlers();
     if (!handlers)
         return; // a future SDK: nothing to hook (no wait tool)
+    if (!host.routesTasks()) {
+        wake.warnOnce("tasks-routing", `wakeshift: this server's @modelcontextprotocol/server is older than ${TASKS_MIN_SERVER} (2.0 to 2.2 answer tasks/get with "Method not found" on protocol 2026-07-28 themselves), so Claude Code's ${WAIT_TOOL} never completes and conversations that use it aren't woken. Upgrade @modelcontextprotocol/server to ${TASKS_MIN_SERVER} or later.`);
+    }
     const call = (raw, args) => {
         const { user, client } = callerOf(raw);
         return toolCallOf(host.req(raw), client, user, args, WAIT_TOOL);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wakeshift/sdk",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "Let agents subscribe to things in your app: Wakeshift wakes them when you emit an event.",
   "license": "Apache-2.0",
   "author": "Clawvisor Inc. <support@wakeshift.ai>",
@@ -62,7 +62,7 @@
   },
   "peerDependencies": {
     "@modelcontextprotocol/sdk": "^1.23.0",
-    "@modelcontextprotocol/server": "^2.0.0",
+    "@modelcontextprotocol/server": "^2.3.0",
     "zod": "^3.25.0 || ^4.0.0",
     "@mastra/mcp": "^2.7.0",
     "xmcp": "^1.9.0"