Give Claude Desktop control of your browser

The problem

• Claude Desktop has no browser. It can reason about a page you paste in, but it cannot open one, click through a flow, or read what is behind a login.
• Headless automation tools spin up a clean browser with no cookies, so every task stalls at a login screen or a CAPTCHA.
• Copying page content back and forth by hand defeats the point of having an agent.

What Vibe MCP changes

• Claude drives the Chrome profile you already use, with your sessions intact — no credentials are ever handed to the model.
• Page content comes back as compact structured text instead of hundreds of kilobytes of raw HTML, so Claude keeps context for the actual task.
• Other agents (Cursor, Codex CLI, Copilot) can stay connected to the same browser at the same time via the Vibe relay.

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 your Claude Desktop config

   Open your Claude Desktop config file and add the "vibe" MCP server, then restart Claude Desktop. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json — Windows: %APPDATA%\Claude\claude_desktop_config.json.

   claude_desktop_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 Claude Desktop gets

How it compares

Claude Desktop browser control — FAQ

Does Claude Desktop support MCP browser control?

Yes. Claude Desktop supports the Model Context Protocol, so any MCP server listed in claude_desktop_config.json becomes available as tools. Vibe MCP exposes browser tools — navigate, click, type, scroll, screenshot, page content, and tab management.

Do I need a separate browser for Claude to use?

No. That is the point of Vibe. Claude drives the Chrome you already have open, using your existing profile and logged-in sessions, instead of launching a clean headless browser with no cookies.

Does Claude get my passwords?

No. Vibe never transmits credentials. The extension acts inside the browser session you already authenticated, so the model sees pages and can act on them, but never receives your passwords.

Can Claude Desktop and Cursor use the browser at the same time?

Yes. Vibe MCP multiplexes multiple agents through a local relay daemon, so Claude Desktop, Cursor, VS Code Copilot, and CLI agents can all be connected to the same browser simultaneously without port conflicts.

Is it free?

The extension and the @vibebrowser/mcp server are free to install and run locally. Everything happens on your machine — automation does not round-trip through a cloud browser.

Works with your other agents too

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