Give Windsurf control of your browser

The problem

• Windsurf can edit code but cannot open and inspect the running app.
• Clean automation browsers cannot reach authenticated environments.

What Vibe MCP changes

• Windsurf drives your existing Chrome profile with sessions intact.
• Multi-agent safe — other MCP clients can stay connected.

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 Windsurf MCP config

   Edit ~/.codeium/windsurf/mcp_config.json, add the "vibe" server, and restart Windsurf.

   ~/.codeium/windsurf/mcp_config.jsonjson

   {
     "mcpServers": {
       "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 Windsurf gets

How it compares

Windsurf browser control — FAQ

Where is the Windsurf MCP config file?

Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Add a "vibe" entry with command npx and args ["-y", "@vibebrowser/mcp"], then restart Windsurf.

Does Windsurf need its own browser?

No. Vibe uses the Chrome you already run, including your logged-in sessions.

Works with your other agents too

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