@miragon/mcp-toolkit-ui 1.0.1 → 1.1.0

package/README.md

@@ -9,7 +9,7 @@ Published to the public npm registry under the `@miragon` scope — no `.npmrc`
 or token needed.
 
 ```sh
-pnpm add @miragon/mcp-toolkit-ui @miragon/mcp-toolkit-core mcp-use@2.0.4 react@19.2.8 react-dom@19.2.8 tailwindcss@4.3.3
+pnpm add @miragon/mcp-toolkit-ui @miragon/mcp-toolkit-core mcp-use@2.1.0 react@19.2.8 react-dom@19.2.8 tailwindcss@4.3.3
 ```
 
 Peer versions are pinned exactly — install the versions above.

package/dist/app/host-bridge.d.ts

@@ -4,7 +4,7 @@ import { type ReactNode } from "react";
  * host runtime. A `HostBridge` is the single seam a portable widget talks to:
  * write the widget against {@link useHostBridge} and it runs unchanged in our
  * own `mcp-use` host, inside ChatGPT (OpenAI Apps SDK), or as a standalone web
- * app driven directly by a `@modelcontextprotocol/sdk` client — only the
+ * app driven directly by a `@modelcontextprotocol/client` client — only the
  * surrounding adapter changes.
  *
  * This is deliberately the *minimum* a deterministic UI needs, not a mirror of
@@ -164,7 +164,7 @@ export declare function createChatGptHostBridge(sdk?: OpenAiAppsSdk | null): Hos
 export interface StandaloneHostBridgeOptions {
     /**
      * The only required capability: how to call a tool on the server. In a
-     * standalone web app this typically wraps a `@modelcontextprotocol/sdk`
+     * standalone web app this typically wraps a `@modelcontextprotocol/client`
      * `Client.callTool({ name, arguments })`, but any function with this shape
      * works — that injection is the whole point: hand-built widgets render
      * against *any* existing MCP server without the toolkit's host runtime.
@@ -197,7 +197,7 @@ export interface StandaloneHostBridgeOptions {
 /**
  * Build a {@link HostBridge} for a standalone web app driven against an existing
  * MCP server — no toolkit host, no `createFrameworkApp`. You inject `callTool`
- * (usually a thin wrapper over a `@modelcontextprotocol/sdk` client); the
+ * (usually a thin wrapper over a `@modelcontextprotocol/client` client); the
  * conversation-shaped verbs (`sendFollowup`, `setModelContext`) are no-ops
  * unless you wire handlers, and `openExternal` defaults to `window.open`.
  *
@@ -207,7 +207,7 @@ export interface StandaloneHostBridgeOptions {
  * harness also builds on this factory so host simulation has a single source.
  *
  * @example
- * const client = new Client(…) // @modelcontextprotocol/sdk
+ * const client = new Client(…) // @modelcontextprotocol/client
  * const bridge = createStandaloneHostBridge({
  *   callTool: (name, args) => client.callTool({ name, arguments: args }),
  *   getData: () => currentRecord,

package/dist/app/host-bridge.js

@@ -173,7 +173,7 @@ export function createChatGptHostBridge(sdk) {
 /**
  * Build a {@link HostBridge} for a standalone web app driven against an existing
  * MCP server — no toolkit host, no `createFrameworkApp`. You inject `callTool`
- * (usually a thin wrapper over a `@modelcontextprotocol/sdk` client); the
+ * (usually a thin wrapper over a `@modelcontextprotocol/client` client); the
  * conversation-shaped verbs (`sendFollowup`, `setModelContext`) are no-ops
  * unless you wire handlers, and `openExternal` defaults to `window.open`.
  *
@@ -183,7 +183,7 @@ export function createChatGptHostBridge(sdk) {
  * harness also builds on this factory so host simulation has a single source.
  *
  * @example
- * const client = new Client(…) // @modelcontextprotocol/sdk
+ * const client = new Client(…) // @modelcontextprotocol/client
  * const bridge = createStandaloneHostBridge({
  *   callTool: (name, args) => client.callTool({ name, arguments: args }),
  *   getData: () => currentRecord,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@miragon/mcp-toolkit-ui",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "description": "React UI for MCP servers: shadcn primitives, composite components, TanStack Query hooks, and the MCP App shell (McpAppView + WidgetRenderer).",
   "repository": {
     "type": "git",
@@ -38,11 +38,11 @@
     "access": "public"
   },
   "peerDependencies": {
-    "mcp-use": "2.0.4",
+    "mcp-use": "2.1.0",
     "react": "19.2.8",
     "react-dom": "19.2.8",
     "tailwindcss": "4.3.3",
-    "@miragon/mcp-toolkit-core": "1.0.1"
+    "@miragon/mcp-toolkit-core": "1.1.0"
   },
   "dependencies": {
     "@base-ui/react": "1.6.0",
@@ -58,13 +58,13 @@
   "devDependencies": {
     "@types/react": "19.2.18",
     "@types/react-dom": "19.2.4",
-    "mcp-use": "2.0.4",
+    "mcp-use": "2.1.0",
     "react": "19.2.8",
     "react-dom": "19.2.8",
     "tailwindcss": "4.3.3",
     "typescript": "6.0.3",
     "vitest": "4.1.10",
-    "@miragon/mcp-toolkit-core": "1.0.1"
+    "@miragon/mcp-toolkit-core": "1.1.0"
   },
   "engines": {
     "node": ">=22.22.2"

package/src/app/host-bridge.tsx

@@ -5,7 +5,7 @@ import { createContext, useContext, type ReactNode } from "react"
  * host runtime. A `HostBridge` is the single seam a portable widget talks to:
  * write the widget against {@link useHostBridge} and it runs unchanged in our
  * own `mcp-use` host, inside ChatGPT (OpenAI Apps SDK), or as a standalone web
- * app driven directly by a `@modelcontextprotocol/sdk` client — only the
+ * app driven directly by a `@modelcontextprotocol/client` client — only the
  * surrounding adapter changes.
  *
  * This is deliberately the *minimum* a deterministic UI needs, not a mirror of
@@ -288,7 +288,7 @@ export function createChatGptHostBridge(sdk?: OpenAiAppsSdk | null): HostBridge
 export interface StandaloneHostBridgeOptions {
   /**
    * The only required capability: how to call a tool on the server. In a
-   * standalone web app this typically wraps a `@modelcontextprotocol/sdk`
+   * standalone web app this typically wraps a `@modelcontextprotocol/client`
    * `Client.callTool({ name, arguments })`, but any function with this shape
    * works — that injection is the whole point: hand-built widgets render
    * against *any* existing MCP server without the toolkit's host runtime.
@@ -322,7 +322,7 @@ export interface StandaloneHostBridgeOptions {
 /**
  * Build a {@link HostBridge} for a standalone web app driven against an existing
  * MCP server — no toolkit host, no `createFrameworkApp`. You inject `callTool`
- * (usually a thin wrapper over a `@modelcontextprotocol/sdk` client); the
+ * (usually a thin wrapper over a `@modelcontextprotocol/client` client); the
  * conversation-shaped verbs (`sendFollowup`, `setModelContext`) are no-ops
  * unless you wire handlers, and `openExternal` defaults to `window.open`.
  *
@@ -332,7 +332,7 @@ export interface StandaloneHostBridgeOptions {
  * harness also builds on this factory so host simulation has a single source.
  *
  * @example
- * const client = new Client(…) // @modelcontextprotocol/sdk
+ * const client = new Client(…) // @modelcontextprotocol/client
  * const bridge = createStandaloneHostBridge({
  *   callTool: (name, args) => client.callTool({ name, arguments: args }),
  *   getData: () => currentRecord,

package/ui-catalog.json

@@ -948,7 +948,7 @@
           "description": "{ callTool (required), getData?, onFollowup?, onOpenExternal?, onModelContext?, theme? }."
         }
       ],
-      "whenToUse": "Build a HostBridge for a standalone web app against any MCP server (callTool usually wraps a @modelcontextprotocol/sdk client). The WidgetFixtureHost builds on this too."
+      "whenToUse": "Build a HostBridge for a standalone web app against any MCP server (callTool usually wraps a @modelcontextprotocol/client client). The WidgetFixtureHost builds on this too."
     },
     {
       "name": "createChatGptHostBridge",