Give Claude Code control of your browser

Verify the feature you just shipped, reproduce a bug on a staging URL, or read a dashboard — from the same terminal session.

Last updated: August 2026

In short

Vibe MCP gives Claude Code browser tools through the Model Context Protocol. Register the @vibebrowser/mcp server once and Claude Code can navigate to a URL, click elements, fill forms, screenshot, and read page content in your real Chrome — including pages behind a login.

The problem

  • Claude Code can write and run code but cannot see the running app in a browser, so "it builds" is as far as verification goes.
  • Wiring Playwright or CDP into every project is plumbing you rewrite each time, and the resulting browser has none of your logins.
  • Screenshotting by hand and pasting images back into the terminal is slow and lossy.

What Vibe MCP changes

  • Claude Code opens your real Chrome, hits the page, and reads it back — closing the write-run-verify loop without extra tooling.
  • Authenticated staging environments, admin panels, and internal tools just work because the session is already yours.
  • Same MCP server as every other client, so behavior is identical across your 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. 2Register the MCP server with Claude Code

    Claude Code reads MCP servers from its own config. Add the "vibe" server the same way you add any stdio MCP server, then start a new session so the tools are picked up.

    terminalbash
    claude mcp add vibe -- npx -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 Code gets

ToolDescription
navigate_to_urlNavigate to any URL
go_back / go_forwardBrowser history navigation
clickClick elements on the page
type / fillEnter text into inputs
scrollScroll the page
take_screenshotCapture screenshots
get_page_contentExtract page text or HTML
get_tabs / create_new_tab / switch_to_tab / close_tabTab management
keyboard_shortcutPress keyboard combinations
web_searchSearch the web

How it compares

FeatureVibe MCPPlaywright MCPBrowserMCP
Multi-agent supportYesNoNo
Uses your browser profileYesNoNo
Logged-in sessionsYesNoNo
No separate browserYesNoNo
Local & privateYesYesPartial
Content-script basedYesNoNo

Claude Code browser control — FAQ

How do I give Claude Code browser access?
Install the Vibe Chrome extension, then register the Vibe MCP server with Claude Code using: claude mcp add vibe -- npx -y @vibebrowser/mcp. Start a new session and Claude Code will have navigate, click, type, screenshot, and page-content tools.
Is this better than Playwright MCP for Claude Code?
For anything behind a login, yes. Playwright launches a fresh browser with no cookies, so authenticated flows fail. Vibe uses your existing Chrome profile and sessions, and unlike Playwright MCP it does not break when a second agent connects.
Can Claude Code use the browser while Claude Desktop is connected?
Yes. Vibe multiplexes agents through a relay daemon, so several MCP clients can control the same browser at once.
Does it work on Windows and Linux?
Yes. The MCP server runs anywhere Node.js runs, and the extension works in Chrome, Brave, Edge, and other Chromium browsers on macOS, Windows, and Linux.

Works with your other agents too

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

Ready to connect Claude Code?

Connecting an agent to your logged-in browser has real privacy consequences. Read what is transmitted, logged and retained in the Privacy Policy.