Vibe Browser for

Give OpenClaw control of your browser

One block in ~/.openclaw/openclaw.json. Paste your Vibe URL under mcpServers, restart, done.

Guide — from OpenClaw docs

These steps follow OpenClaw's public MCP config docs: remote servers are mcpServers entries with a url in ~/.openclaw/openclaw.json. We have not live-tested this exact pairing yet, so treat it as a guide.

Setup steps

  1. 1Install the Vibe extension in Chrome

    Add Vibe AI Browser from the Chrome Web Store (Chrome, Brave, Edge, or any Chromium browser). This is the piece that lets an agent drive the browser you are already logged into — no second browser profile, no re-authentication.

  2. 2Copy your agent connection URL from the extension

    Click the Vibe icon → Settings → turn on "Enable external AI agent control" → choose Remote (internet) → copy the Agent connection URL. The last path segment is your routing UUID. The connector URL is https://relay.api.vibebrowser.app/mcp/ followed by that UUID. Leave the extension running and remote control on — the connector talks to this browser, so if it is closed there is nothing on the other end.

    Vibe extension → Settings → Agent connection URLurl
    https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
    Vibe extension Settings, AI Agent Control section, with the masked Agent connection URL and its Copy button
  3. 3Add Vibe to ~/.openclaw/openclaw.json and restart

    Open ~/.openclaw/openclaw.json and add the "vibe" entry below under mcpServers (keep your other servers — just add this one). Restart OpenClaw. The Vibe tools load on startup.

    ~/.openclaw/openclaw.jsonjson
    {
      "mcpServers": {
        "vibe": {
          "url": "https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>"
        }
      }
    }

Your relay URL / extension UUID grants live control of your browser session. Treat it like a password: never commit it or paste it into a shared chat.

Check it works

Ask OpenClawbash
List the tabs I have open in my browser right now.

Expected answer: your real open Chrome tabs

Ask it in any OpenClaw chat after the restart. OpenClaw cannot know your tabs on its own, so a correct list proves the connector works. You can also watch the startup log — MCP servers list their tools as OpenClaw boots.

Quick answers

Where does the config go?
In ~/.openclaw/openclaw.json, inside the mcpServers block. If the file already has servers, add "vibe" next to them — do not replace the block.
Do I need to install a local MCP server?
No. Vibe is a remote MCP server — OpenClaw connects to the URL directly. The only thing you install is the Vibe Chrome extension.
The tools did not load — what now?
Check three things: the URL ends with your full routing UUID, Chrome is open with the extension running, and external AI agent control is on with Remote (internet) mode. Then restart OpenClaw again.

Ready to connect OpenClaw?