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.
Run claude mcp add vibe -- npx -y @vibebrowser/mcp, then start a new session so the tools are picked up. Claude Code gets navigate, click, type, screenshot, and page-content tools.
Claude Code can write and run code but cannot see the running app. With Vibe it 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 — no re-authentication.
Wiring Playwright or CDP into every project is plumbing you rewrite each time, and the resulting browser has none of your logins. One MCP server replaces it.
Run claude mcp add vibe -- npx -y @vibebrowser/mcp, then start a new session so the tools are picked up. Claude Code gets navigate, click, type, screenshot, and page-content tools.
Claude Code can write and run code but cannot see the running app. With Vibe it 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 — no re-authentication.
Wiring Playwright or CDP into every project is plumbing you rewrite each time, and the resulting browser has none of your logins. One MCP server replaces it.
Vibe multiplexes agents through a relay daemon, so several MCP clients can control the same browser at once — and the same server behaves identically across your agents.
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.
Ask Claude Code to open the feature it just shipped and verify it works
Have Claude Code reproduce a bug on a staging URL and report what it sees
Ask Claude Code to read a dashboard and bring the numbers into your session
Let Claude Code screenshot a page and check the layout after a change
Have Claude Code fill a form in your browser to test a flow end to end
Google Workspace, MCP access for other agents, reusable skills, and a secure secrets vault.
Gmail + Calendar actions built in for real workflows, not brittle APIs.
Expose your browser as an MCP server so other AI agents can drive it.
Securely connect remote agents to your logged-in browser without VPNs.
Create reusable skills and share them across your team or clients.
Internal vault with a password-fill tool that never exposes secrets to the LLM.
Works with Vibe AI, Anthropic Claude Max, GitHub Copilot, and BYOK providers.
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.
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.
Yes. Vibe multiplexes agents through a relay daemon, so several MCP clients can control the same browser at once.
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.