js-bridge-mcp 0.1.0 → 0.1.6

package/README.md

@@ -30,6 +30,18 @@ to write one for a new page.
 
 ## Run it
 
+### Via npx
+
+```bash
+npx js-bridge-mcp
+```
+
+Starts the MCP + WS + `main.js` server on port 8766. Point an MCP client at
+`http://localhost:8766/mcp`, then serve `legacy-page/hello-world.html` (or
+your own page) with any static file server.
+
+### From this repo
+
 ```bash
 npm run build        # bundle src/client/main.ts -> dist/client/main.js
 npm run start:mcp     # MCP + WS + main.js server, port 8766

package/dist/src/tools/hello-tools.js

@@ -1,26 +1,26 @@
 import { z } from 'zod';
 const getEmbedSnippet = {
     name: 'get_embed_snippet',
-    description: 'Returns a single line of executable JavaScript that connects the current page to this ' +
-        'MCP session\'s tenant. Primary use: paste it directly into the browser\'s DevTools console ' +
-        '(Chrome/Firefox/etc.) on the target page and press enter — no editing the page\'s source ' +
-        'required. It can also be wrapped in a <script type="module">...</script> tag if the user ' +
-        'wants to bake it into the page\'s HTML instead (e.g. right before </body>). Either way, once ' +
-        'it runs, the page pushes its own tool manifest (window.__mcpTools, plus an optional ' +
-        'window.__mcpSummary string with shared cross-tool context — see the describe_tools tool once ' +
-        'connected) to this session\'s tenant, and the tools it declares become available to call from ' +
-        'THIS conversation. By default this server shares one tenant across every MCP session that ' +
-        'doesn\'t explicitly pin one (this keeps a single browser connection stable across an agent ' +
-        'harness\'s own session churn) — so unless the server was started with per-session tenants, ' +
-        'pages bridged from different conversations end up on the same tenant and see each other\'s ' +
-        'tools rather than staying isolated. Running the snippet immediately opens a browser prompt() ' +
-        'asking the user to name this connection (pre-filled with the page title) — warn the user ' +
-        'about this pop-up before they paste it so it isn\'t a surprise, and know that ' +
-        'dismissing/cancelling it is safe (falls back to the page title, connection proceeds either ' +
-        'way). The chosen name becomes this connection\'s tool-name prefix once a second connection ' +
-        'joins the same tenant (see describe_tools). Share the returned snippet with the user and tell ' +
-        'them to open DevTools on the target page, go to the Console tab, paste it, and press enter; do ' +
-        'not construct this URL by hand.',
+    description: 'Returns a single line of executable JavaScript that connects the current page to this MCP session\'s ' +
+        'channel. Paste it directly into the browser DevTools console on the target page and press enter — no ' +
+        'source edits needed (or wrap in <script type="module">...</script> before </body> to bake it into the ' +
+        'page). Once run, the page pushes its tool manifest (window.__mcpTools, optional window.__mcpSummary — see ' +
+        'describe_tools) to this session\'s channel, and its tools become callable from THIS conversation. Share ' +
+        'the snippet and tell the user to paste it in DevTools\' Console tab and press enter; do not construct the ' +
+        'URL by hand. ' +
+        '\n\n' +
+        'DEFAULT TO calling join_channel with a topic-scoped name (e.g. "bulletino", from the page/app or task) ' +
+        'BEFORE this — the normal path, not something reserved for when it happens to matter. Skip only for a ' +
+        'genuinely one-off bridge, or when nothing suggests a name worth giving it: staying on "default" means ' +
+        'sharing state with every other unnamed session on this server, and blocks another agent from reconnecting ' +
+        'to the SAME bridged page later by name. The snippet is generated fresh from whatever channel this session ' +
+        'is on, so join first, then call this. Reusing an already-generated snippet in a second tab connects that ' +
+        'tab to the SAME channel, not a new one — join a different name and call this again for a distinct one. ' +
+        '\n\n' +
+        'Running the snippet opens a browser prompt() asking the user to name this connection (pre-filled with the ' +
+        'page title) — warn them before they paste it; dismissing is safe (falls back to the page title). That ' +
+        'name becomes this connection\'s tool-name prefix once a second connection joins the same channel (see ' +
+        'describe_tools).',
     schema: {},
     handler: async (_args, tenant, port) => {
         const tenantId = tenant().id;

package/dist/src/tools/register.js

@@ -1,6 +1,7 @@
-import { createManifestToolRegistry } from 'mcp-tenant-lib';
+import { createManifestToolRegistry, registerChannelTools } from 'mcp-tenant-lib';
+import { initialHelloState } from '../types.js';
 import { helloTools } from './hello-tools.js';
-export function registerHelloTools(mcp, tenant, port) {
+export function registerHelloTools(mcp, tenant, port, setChannel) {
     for (const tool of helloTools) {
         mcp.tool(tool.name, tool.description, tool.schema, (args) => tool.handler(args, tenant, port));
     }
@@ -11,6 +12,26 @@ export function registerHelloTools(mcp, tenant, port) {
     // multiple concurrent MCP sessions' McpServer/registry pairs can be
     // bound to the same tenant at once and all need to stay in sync, not
     // just whichever one connected last.
-    tenant().addManifestToolRegistry(registry);
-    mcp.server.onclose = () => tenant().removeManifestToolRegistry(registry);
+    //
+    // Track which Tenant object the registry is currently subscribed to so a
+    // later join_channel (see the wrapped setChannel below) can move the
+    // subscription — tenant() is a live accessor that starts pointing at a
+    // different Tenant once the session retargets to a named channel, but the
+    // subscription itself does NOT follow automatically: addManifestToolRegistry
+    // only runs once here, against whichever tenant was current at connect
+    // time. Without migrating it, a page that bridges into a channel AFTER
+    // join_channel was called would push its manifest to a tenant nothing is
+    // subscribed to — describe_tools would still see it (it reads
+    // tenant().toolManifest fresh every call), but no real MCP tool would ever
+    // get registered for it.
+    let subscribedTenant = tenant();
+    subscribedTenant.addManifestToolRegistry(registry);
+    mcp.server.onclose = () => subscribedTenant.removeManifestToolRegistry(registry);
+    const setChannelAndMigrateRegistry = (id) => {
+        setChannel(id);
+        subscribedTenant.removeManifestToolRegistry(registry);
+        subscribedTenant = tenant();
+        subscribedTenant.addManifestToolRegistry(registry);
+    };
+    registerChannelTools(mcp, tenant, port, setChannelAndMigrateRegistry, undefined, { ...initialHelloState });
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "js-bridge-mcp",
-  "version": "0.1.0",
+  "version": "0.1.6",
   "type": "module",
   "description": "Generic bridge: exposes MCP tools discovered from a connected page's own JSON tool manifest, dispatched over a cross-origin WebSocket. Ships a hello-world example page under legacy-page/.",
   "repository": {
@@ -35,7 +35,7 @@
     "test": "node --import tsx --test test/**/*.test.ts"
   },
   "dependencies": {
-    "mcp-tenant-lib": "^0.1.0",
+    "mcp-tenant-lib": "^0.3.3",
     "@modelcontextprotocol/sdk": "^1.12.0",
     "ws": "^8.18.0",
     "zod": "^3.23.8"