Give OpenCode control of your browser

The problem

• OpenCode can run code but cannot verify the result in a browser.
• Authenticated environments are unreachable from a clean automation browser.

What Vibe MCP changes

• OpenCode drives your existing Chrome with your sessions intact.
• Shares the browser with other connected agents.

Install in 3 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. 2Add Vibe to .opencode/config.json

   Register the "vibe" MCP server in your OpenCode config and restart OpenCode.

   .opencode/config.jsonjson

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

3. 3Connect the extension and run your first command

   Click the Vibe icon, open Settings, and enable "MCP External Control" until the status reads Connected. Then ask your agent to open a page and take a snapshot — it should return the content of your real tab.

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.

Tools OpenCode gets

How it compares

OpenCode browser control — FAQ

How do I add an MCP server to OpenCode?

Add it under mcp.servers in .opencode/config.json. For Vibe, use command npx with args ["-y", "@vibebrowser/mcp"], then restart OpenCode.

Does OpenCode share the browser with other agents?

Yes. Vibe multiplexes MCP clients through a relay daemon so several agents can drive one browser simultaneously.

Works with your other agents too

The same MCP server powers every client. Multiple agents can drive the same browser at once.