@empir3/empir3-bridge 0.3.21 → 0.3.22

package/CHANGELOG.md

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.3.22] - 2026-06-21
+
+### Added
+- **`empir3-bridge-mcp` bin** — run the MCP stdio server straight from the published npm package, no clone required. Wire it into any MCP client's `.mcp.json` with `npx -y -p @empir3/empir3-bridge empir3-bridge-mcp`. Runs `src/mcp-server.ts` through the bundled `tsx`; the companion `empir3-bridge` bin still starts the daemon directly.
+
 ### Changed
 - Published to npm as `@empir3/empir3-bridge`.
 

package/README.md

@@ -101,13 +101,34 @@ npm install
 npm start
 ```
 
+Or install the published package from npm:
+
+```bash
+npm install -g @empir3/empir3-bridge
+empir3-bridge            # starts the bridge + Chrome  (empir3-bridge --status / --kill to manage)
+```
+
 Open the dashboard:
 
 ```text
 http://localhost:3006
 ```
 
-Then add the bridge to a Claude Code project with `.mcp.json`:
+Then add the bridge to a Claude Code project with `.mcp.json`. Using the published package (no clone needed):
+
+```json
+{
+  "mcpServers": {
+    "empir3-bridge": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "-p", "@empir3/empir3-bridge", "empir3-bridge-mcp"]
+    }
+  }
+}
+```
+
+Or point it at a local clone (for development):
 
 ```json
 {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@empir3/empir3-bridge",
-  "version": "0.3.21",
+  "version": "0.3.22",
   "description": "Local-first browser and desktop control bridge for AI agents using MCP.",
   "license": "MIT",
   "author": "Empir3",
@@ -27,7 +27,8 @@
     "local-first"
   ],
   "bin": {
-    "empir3-bridge": "./src/launch.js"
+    "empir3-bridge": "./src/launch.js",
+    "empir3-bridge-mcp": "./src/mcp-entry.js"
   },
   "main": "./src/cli.ts",
   "scripts": {

package/src/mcp-entry.js

@@ -0,0 +1,55 @@
+#!/usr/bin/env node
+/**
+ * empir3-bridge-mcp — stdio MCP server entry for the published npm package.
+ *
+ * MCP clients (Claude Code, Codex, Cursor, …) launch this with:
+ *   npx -y -p @empir3/empir3-bridge empir3-bridge-mcp
+ *
+ * It runs src/mcp-server.ts through the bundled `tsx` with stdio inherited, so
+ * the MCP client speaks JSON-RPC straight to the server over stdin/stdout. The
+ * MCP server auto-launches the bridge (HTTP wrapper + CDP) on first tool use,
+ * so no separate daemon step is required.
+ *
+ * The companion `empir3-bridge` bin starts the daemon directly (src/launch.js);
+ * this one is the thin MCP shim.
+ */
+'use strict';
+
+const { spawn } = require('child_process');
+const path = require('path');
+
+let tsxCli;
+try {
+  // Resolves tsx from the package's own node_modules regardless of cwd, the
+  // same mechanism src/launch.js relies on. tsx is a runtime dependency.
+  tsxCli = require.resolve('tsx/cli');
+} catch (err) {
+  process.stderr.write(
+    '[empir3-bridge-mcp] could not resolve tsx — reinstall the package: npm i -g @empir3/empir3-bridge\n'
+  );
+  process.exit(1);
+}
+
+const mcpServer = path.join(__dirname, 'mcp-server.ts');
+
+const child = spawn(process.execPath, [tsxCli, mcpServer, ...process.argv.slice(2)], {
+  stdio: 'inherit',
+});
+
+child.on('error', (err) => {
+  process.stderr.write(`[empir3-bridge-mcp] failed to start MCP server: ${err.message}\n`);
+  process.exit(1);
+});
+
+child.on('exit', (code, signal) => {
+  if (signal) {
+    try { process.kill(process.pid, signal); } catch { process.exit(1); }
+  } else {
+    process.exit(code == null ? 0 : code);
+  }
+});
+
+// Forward termination so the MCP client closing the pipe tears down the server.
+for (const sig of ['SIGINT', 'SIGTERM', 'SIGHUP']) {
+  process.on(sig, () => { try { child.kill(sig); } catch {} });
+}