@wp-playground/remote 3.1.51 → 3.1.53

package/lib/playground-client.d.ts

@@ -5,8 +5,10 @@ import type { ProgressReceiver } from '@php-wasm/progress';
 import type { MessageListener, UniversalPHP } from '@php-wasm/universal';
 import type { RemoteAPI, SyncProgressCallback } from '@php-wasm/web';
 import type { ProgressBarOptions } from './progress-bar';
+import type { WebMCPToolDescriptor } from './webmcp-frame-bridge';
 import type { PlaygroundWorkerEndpoint, MountDescriptor, WorkerBootOptions } from './playground-worker-endpoint';
 export type { BootProgressEvent } from './playground-worker-endpoint';
+export type { WebMCPToolDescriptor } from './webmcp-frame-bridge';
 export interface WebClientMixin extends ProgressReceiver {
     /**
      * Sets the progress bar options.
@@ -49,6 +51,23 @@ export interface WebClientMixin extends ProgressReceiver {
      * @param flags The iframe sandbox flags.
      */
     setIframeSandboxFlags(flags: string[]): Promise<void>;
+    /**
+     * Subscribes to the WebMCP tools a plugin registers with
+     * `document.modelContext` inside the WordPress document.
+     *
+     * The callback receives the complete tool list every time it changes, and
+     * once with the current list when it subscribes. A navigation to a page
+     * that registers no tools reports an empty list.
+     */
+    onWebMCPToolsChanged(fn: (tools: WebMCPToolDescriptor[]) => void): Promise<void>;
+    /**
+     * Runs one of those tools inside the WordPress document and returns its
+     * JSON-serializable result.
+     *
+     * @param name The tool name as announced by `onWebMCPToolsChanged`.
+     * @param args The tool input.
+     */
+    callWebMCPTool(name: string, args: Record<string, unknown>): Promise<unknown>;
     /**
      * The onDownloadProgress event listener.
      */

package/lib/webmcp-frame-bridge.d.ts

@@ -0,0 +1,30 @@
+/**
+ * A tool a plugin registered with `document.modelContext` inside the
+ * WordPress document, as seen from outside that document.
+ *
+ * `execute` does not survive the frame boundary, so only the descriptive
+ * fields are carried over. Calls travel back through `callWebMCPTool()`.
+ */
+export interface WebMCPToolDescriptor {
+    name: string;
+    description: string;
+    inputSchema?: Record<string, unknown>;
+    annotations?: {
+        readOnlyHint?: boolean;
+        destructiveHint?: boolean;
+    };
+}
+export interface WebMCPFrameBridge {
+    subscribe(listener: (tools: WebMCPToolDescriptor[]) => void): void;
+    callTool(name: string, args: Record<string, unknown>): Promise<unknown>;
+}
+/**
+ * Mirrors the WordPress document's WebMCP tools into this frame and forwards
+ * tool calls back into it.
+ *
+ * The WordPress document owns the registry because the remote frame cannot
+ * read its DOM under Document-Isolation-Policy. Each announcement carries the
+ * full tool list and replaces the previous one, so a navigation that registers
+ * no tools clears the list.
+ */
+export declare function createWebMCPFrameBridge(wpFrame: HTMLIFrameElement): WebMCPFrameBridge;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@wp-playground/remote",
-	"version": "3.1.51",
+	"version": "3.1.53",
 	"description": "WordPress Playground remote host",
 	"repository": {
 		"type": "git",
@@ -25,5 +25,5 @@
 		"access": "public",
 		"directory": "../../../dist/packages/playground/remote"
 	},
-	"gitHead": "a18fe6b003d7c8ab12441297eca0f525cce7e3e6"
+	"gitHead": "8cd60ace8c3d32c8cb2b569b7471fdd98f88013e"
 }