Vibe MCP

Paste the block below into yourOpenClaworHermesagent. Replace the last line with your remote value — the connector URL (https://relay.api.vibebrowser.app/mcp/<uuid>) shown in the Vibe extension'sSettings → AI Agent Control → Remote (internet) → Relay access(a bare UUID or awss://relay URL also still work). That's the only edit you make.

You are setting yourself up to control my real Chrome through Vibe Browser. Work through the steps in order, and after each step confirm it worked before moving on. Do not claim a step is done until you have proven it. 1. Install the "vibebrowser" skill for your runtime: - OpenClaw: npx -y skills add VibeTechnologies/vibe-mcp -s vibebrowser -a openclaw -g -y --copy --dangerously-accept-openclaw-risks then run openclaw skills list and confirm a "vibebrowser" row shows "ready" as installer registration. - Hermes: npx -y skills add VibeTechnologies/vibe-mcp -s vibebrowser -y optional installer registration check: npx -y skills list shows a "vibebrowser" row. 2. Remember my remote so I only give it to you once. Save it to a file vibebrowser-cli.md in your persistent agent workspace root (the directory that holds your memory/ folder — not the shell's working dir, not $HOME unless they are the same) as a line remote: <value>; if your runtime can also write memory keys, additionally store it under vibebrowser_remote. On every later command — including the first message of a new conversation — load it back from that file and reuse it without asking me again. 3. Record a standing rule so you route correctly later: whenever I ask you to do anything in MY browser / MY Chrome / MY tabs / the page I'm on, use this vibebrowser skill (npx -y @vibebrowser/cli@latest with my saved remote) to drive my REAL browser — never your built-in, headless, or in-pod browser, never web-fetch instead, and never run vibebrowser. Save this rule wherever your standing instructions/memory live so it applies in future conversations. 4. Confirm you can control my Chrome, retrying on "Extension reconnecting" (wait 3s, up to 5x): npx -y @vibebrowser/cli@latest --remote "<my remote>" --json status --wait-for-extension --wait-timeout 20000 npx -y @vibebrowser/cli@latest --remote "<my remote>" --json snapshot --format aria Then report: (1) is extensionConnected true, (2) did the snapshot return my real page content? My remote: <PASTE YOUR CONNECTOR URL, UUID, OR wss:// URL HERE>

The browser-automation MCP space moved fast. Most of what used to differentiate us is now table stakes — so here is an honest scorecard. Where a competitor matches us, the column saysYes.

- Outbound, cross-machine control.The Vibe extension opens an outbound WebSocket to a relay (wss://relay.api.vibebrowser.app/<uuid>). Nothing listens on the user's machine, nothing is port-forwarded, and the agent can live in a pod, a cron job, or a chat bot. No competitor documents an extension-initiated outbound connection to a remote MCP server.
- Real profile without the dialog tax.Chrome DevTools MCP needs approval foreachWebSocket connection to Chrome (](https://vibebrowser.app)#1794, open; persistence wasclosed won't-fix). The maintainer's workaround —--remote-debugging-portwith a dedicated--user-data-dir— avoids the dialog by giving up your logged-in profile. So:skip the dialog, or use your real profile — not both.

- Vendor lock-in.Claude for Chrome is GA, clicks and types via thedebuggerpermission, and supports scheduled tasks — it is the closest competitor. But it only drives Anthropic's own surfaces (side panel, Claude Desktop connector, Cowork, Claude Code). There is no public API or MCP surface, so Codex, OpenCode, Hermes and OpenClaw cannot use it. Vibe MCP is agent-agnostic.
- Stability.Chrome DevTools MCP is explicitly experimental and currently carries open memory-leak (#2431,#2291,#2456) and concurrency (#1763,#1921) issues.

Claude Desktop Cursor VS Code OpenCode | | | | v v v v [vibebrowser-mcp] [vibebrowser-mcp] [vibebrowser-mcp] [vibebrowser-mcp] | | | | +------------------+----------------+---------------+ | v [Relay Daemon] <-- Auto-spawned, handles multiplexing | v [Vibe Extension] | v [Your Chrome]

- Multi-Agent Ready- Run Claude, Cursor, VS Code, and more simultaneously against one browser
- Uses Your Browser- No separate browser instance, uses your existing Chrome with all your logins
- Remote-capable- The extension dials out to a relay, so the agent can run on another machine with no inbound port
- Local by default- In local mode everything stays on127.0.0.1; only remote relay mode routes traffic throughrelay.api.vibebrowser.app
- Direct Chrome DevTools mode- Extension tools stay primary by default; use--devtoolsto drive your real running Chrome directly over the DevTools Protocol (no extension required)

Install the Vibe AI Browser extension in Chrome, Brave, or any Chromium browser:

Option A: Chrome Web Store (Recommended)
- Visit theChrome Web Store
- Click "Add to Chrome"
- The Vibe icon will appear in your toolbar
- Download thelatest release ZIP
- Extract to a permanent folder
- Go tochrome://extensions, enable Developer Mode
- Click "Load unpacked" and select the extracted folder

For detailed instructions, see theinstallation guide.

{ "mcpServers": { "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } } }

- Open Cursor Settings (Cmd/Ctrl + ,)
- Go to "Features" -> "MCP Servers"
- Click "Add Server" and add:

{ "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } }

{ "github.copilot.chat.mcpServers": { "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } } }

Edit~/.codeium/windsurf/mcp_config.json:

{ "mcpServers": { "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } } }

{ "mcp": { "servers": { "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } } } }

{ "mcpServers": { "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } } }

All three share one config file:~/.codex/config.toml. Configure once, use everywhere.

codex mcp add vibe -- npx -y @vibebrowser/mcp

Or add the table to~/.codex/config.tomlby hand (Codex usesTOML, not JSON):

[mcp_servers.vibe] command = "npx" args = ["-y", "@vibebrowser/mcp"]

In the ChatGPT desktop app you can also use the UI:Settings → MCP servers → Add server, chooseSTDIO, commandnpx, args-y @vibebrowser/mcp, thenRestart.

Verify withcodex mcp list, or type/mcpin the Codex TUI or the desktop composer.

ChatGPT on the web does not read local Codex config, so a local MCP server like Vibe is not available there.

Use the shortest direct package invocation for the MCP server:

npx -y @vibebrowser/mcp@latest --help npx -y @vibebrowser/mcp@latest start --transport http npx -y @vibebrowser/mcp@latest openclaw --remote "$VIBE_REMOTE_URL"

Backward-compatible aliases still work when you need explicit binaries:

npx -y -p @vibebrowser/mcp@latest vibebrowser-mcp --help npx -y -p @vibebrowser/mcp@latest vibe-mcp --help

Everything above assumes the client can spawn a local process. Hosted assistants cannot: Claude on the web / in Cowork / on mobile, and ChatGPT on the web, run in the vendor's cloud with no access to your machine. They accept aremote MCP server URLand nothing else — no command, no arguments, and no custom request headers.

For those, skip@vibebrowser/mcpentirely. The extension alone is enough:

https://relay.api.vibebrowser.app/mcp/<your-extension-uuid>

Find<your-extension-uuid>in the extension:Vibe icon → Settings → AI Agent Control → Remote (internet) → Relay access. That panel shows this exact connector URL, and the same string is now thepreferredvalue for the CLI/server--remoteflag — paste it in both places, no translation needed:

VIBE_REMOTE_URL="https://relay.api.vibebrowser.app/mcp/00000000-0000-0000-0000-000000000000" npx -y @vibebrowser/mcp@latest start --remote "$VIBE_REMOTE_URL"

A bare extension UUID or awss://relay.api.vibebrowser.app/<uuid>relay URL are still accepted as advanced/compatibility forms — see the accepted--remotevalues table in "Cloud OpenClaw -> Local Browser" below.

This is a plainStreamable HTTPMCP endpoint. There isno OAuth consent flow, no dynamic client registration, and no scope setupon this path — the UUID in the URL (or header, below) is the entire credential. If a client insists on an OAuth login before it will add the server, that client is not supported here; use the local stdio path instead.

Custom connectors are a paid-plan feature in the Claude and ChatGPT products.

Codex Desktop, Codex CLI and the Codex IDE extension can spawn a local process, and they all share~/.codex/config.toml. Prefer the local stdio entry above — it keeps traffic on127.0.0.1and keeps the UUID out of a URL. Usecodex mcp add vibe --url …only when the browser you want to drive is on a different machine from Codex. The ChatGPTdesktop appis Codex-backed and reads the same config, so it is a local-stdio surface too; only ChatGPTwebneeds the hosted URL.