mcp-chrome-vibemaker-bridge

Node.js Native Messaging host that connects Claude Code (or any MCP client) to your live Chrome browser via the mcp-chrome-vibemaker extension.

This is the vibemaker fork of mcp-chrome-bridge, adding Force Reconnect, a Playwright CDP fallback launcher, dynamic-port negotiation, and self-healing diagnostics.

Install

npm install -g mcp-chrome-vibemaker-bridge

The postinstall step will:

1. Register the Chrome Native Messaging host (user-level, no sudo).
2. Download the matching Chrome extension to ~/Downloads/mcp-chrome-vibemaker-extension-v<version>/.
3. Print the next-step instructions for loading the extension and wiring chrome-mcp-stdio into your .mcp.json.

Wire into Claude Code

Paste this into Claude Code once after install:

Register chrome-mcp-stdio in .mcp.json with command: "node", args: ["<npm root -g>/mcp-chrome-vibemaker-bridge/dist/mcp/mcp-server-stdio.js"], env: { "CHROME_PORT": "12316" }. Run npm root -g first to resolve the path. Preserve any existing servers.

Then run /mcp in Claude Code to confirm chrome-mcp-stdio is connected.

Load the Chrome extension

1. Open chrome://extensions
2. Enable Developer mode
3. Click Load unpacked and select ~/Downloads/mcp-chrome-vibemaker-extension-v<version>/

The extension ID is fixed at epadcnnkkmnhalmhlemjlompmggbfjfa via a pinned manifest.key, so every install gets the same ID.

Diagnostics

mcp-chrome-vibemaker-bridge doctor        # health check
mcp-chrome-vibemaker-bridge doctor --fix  # attempt auto-repair
mcp-chrome-vibemaker-bridge report --copy # copy a diagnostic report to clipboard

Supported platforms

| OS | Chrome | Chromium | | ------- | ------ | -------- | | macOS | ✓ | ✓ | | Linux | ✓ | ✓ | | Windows | ✓ | ✓ |

Links

• Source & issues: https://github.com/bambwc20/mcp-chrome-vibemaker
• Releases: https://github.com/bambwc20/mcp-chrome-vibemaker/releases
• Upstream: https://github.com/hangwin/mcp-chrome

License

MIT