@mcpcloud/runtime 0.12.4 → 0.15.0

package/dist/tool-errors.d.ts

@@ -23,7 +23,18 @@
  * keep the two in step, and see `toolErrorsBuilder.test.ts`, which pins the
  * parts that must not drift.
  */
-import type { CallToolResult } from '@modelcontextprotocol/sdk/types.js';
+import type { CallToolResult } from '@modelcontextprotocol/server';
+import type * as McpSdk from '@modelcontextprotocol/server';
+/**
+ * The SDK's `inputRequired` builder, INJECTED rather than imported as a value.
+ *
+ * Typed off the SDK so the shape is exact, but reached only through a
+ * type-only import, which is erased. This module therefore stays free of any
+ * runtime dependency on the MCP SDK — it is the one place tool failures are
+ * classified, and keeping it importable without standing a server up is worth
+ * threading one parameter for.
+ */
+export type InputRequiredBuilder = typeof McpSdk.inputRequired;
 export type ToolErrorClass = 
 /** Arguments were rejected before the request left us. Fix the call, not the code. */
 'BINDING_MISUSE'
@@ -71,7 +82,7 @@ export declare function classifyToolError(error: unknown): ToolErrorMeta;
  * prompts). Swallowing it into an `isError` result would silently break
  * elicitation, so this check gates the catch below.
  *
- * Deliberately structural rather than `instanceof McpError`. Generated bundles
+ * Deliberately structural rather than `instanceof ProtocolError`. Generated bundles
  * throw this from the vendored `runtime/mcp-runtime.js`, which carries its own
  * copy of the SDK classes — an `instanceof` against the npm copy would be false
  * there, and elicitation would break silently in exactly the servers that use
@@ -88,6 +99,15 @@ export declare function mustRethrow(error: unknown): boolean;
 export declare function toToolErrorResult(error: unknown): CallToolResult;
 /**
  * Run a tool handler, converting a throw into a classified error result.
- * Elicitation errors pass straight through.
+ *
+ * URL elicitation is the one failure that must reach the client intact rather
+ * than becoming an `isError` result — the caller has to act on it. Which SHAPE
+ * it takes depends on the protocol era, and the two are incompatible: 2025
+ * clients expect the `-32042` error and 2026-07-28 clients cannot be sent one
+ * at all. Legacy (the default) rethrows exactly as before; modern converts to
+ * the `input_required` result the revision defines.
  */
-export declare function runToolHandler(invoke: () => Promise<CallToolResult>): Promise<CallToolResult>;
+export declare function runToolHandler(invoke: () => Promise<CallToolResult>, options?: {
+    era?: 'legacy' | 'modern';
+    inputRequired?: InputRequiredBuilder;
+}): Promise<CallToolResult>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcpcloud/runtime",
-  "version": "0.12.4",
+  "version": "0.15.0",
   "description": "MCPCloud generated-server runtime: transports, config, upstream auth/HTTP, validation, projection, and discovery for MCP servers built on MCPCloud.",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",
@@ -36,11 +36,12 @@
   "dependencies": {
     "@jitl/quickjs-ffi-types": "^0.32.0",
     "@metrichor/jmespath": "^0.3.1",
-    "@modelcontextprotocol/sdk": "^1.29.0",
+    "@modelcontextprotocol/server": "^2.0.0",
     "quickjs-emscripten-core": "^0.32.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {
+    "@modelcontextprotocol/client": "^2.0.0",
     "typescript": "^5.9.3",
     "vitest": "^3.2.4"
   },