How is Vibe MCP different from Playwright MCP, Chrome DevTools MCP, and BrowserMCP?

Playwright MCP and Chrome DevTools MCP launch a separate browser by default. Playwright now offers a Chrome extension mode to connect to your existing browser, but it still lacks multi-agent support, Google Workspace tools, credential vault, and sub-agent orchestration. Chrome DevTools MCP requires --remote-debugging-port and sends telemetry to Google. BrowserMCP is a Chrome extension like Vibe but only supports a single agent, has ~13 tools, and its extension is closed-source. Vibe MCP supports multiple agents simultaneously, offers 25+ tools, includes Google Workspace integration, a credential vault, sub-agent orchestration, and uses markdown-indexed page content for 3-5x lower token usage.

Can multiple AI agents control the browser at the same time?

Yes. Vibe MCP uses a relay daemon architecture where multiple AI clients (Claude, Cursor, VS Code, etc.) connect via WebSocket to a shared relay, which forwards requests to the Vibe extension. Each agent gets its own stdio MCP bridge.

Does Vibe MCP require Chrome debug permissions?

No. Vibe MCP uses content scripts and the Chrome Extensions API — no --remote-debugging-port or CDP required. Playwright MCP's extension mode also avoids debug ports, but its default mode still launches a separate browser. Chrome DevTools MCP requires debug ports. Vibe works with your normal browser profile without any special launch flags.

What AI agents work with Vibe MCP?

Vibe MCP works with any MCP-compatible AI client including Claude Desktop, Cursor, VS Code (GitHub Copilot), OpenCode, Claude Code, Windsurf, and Gemini CLI. Setup requires adding one JSON config block.

How does the markdown-indexed page content work?

Instead of sending raw DOM or accessibility tree snapshots, Vibe extracts page content as clean markdown with interactive elements labeled as [index:score]. Agents use these indices to click, fill, and interact with elements. This drastically reduces token usage and context pollution compared to full page snapshots.

Why does it matter that Vibe uses my real browser?

Playwright MCP and Chrome DevTools MCP launch a fresh, separate browser by default with no sessions, cookies, or extensions. Playwright now offers a Chrome extension mode that can connect to your existing browser, but setup requires token-based auth and it still lacks multi-agent support. Vibe MCP connects directly to the browser you are already using with zero configuration, so agents can interact with Gmail, Slack, GitHub, Jira, or any logged-in site without re-authenticating.

Model Context Protocol

Control Your Browser from
Any AI Agent|

Connect Claude, Cursor, VS Code, and more to your real browser — with all your sessions, cookies, and extensions intact. Multi-agent ready, internet-exposed relay, 25+ tools, open source MCP server. Connect any agent on the internet — including OpenClaw — to your local browser.

CLI

claude mcp add --transport stdio vibe -- npx -y @vibebrowser/mcp

Or add to project-level .mcp.json

Requires Node.js and the Vibe Browser extension

25+ browser toolsMulti-agent relayInternet-exposed relayNo debug permissionsOpen source MCP

Works with any MCP-compatible agent

Claude Code

OpenCode

Cursor

Claude Desktop

VS Code

Windsurf

Gemini CLI

Codex

OpenClaw

How Vibe MCP compares

Vibe MCP is the only browser MCP that uses your real browser with all your logged-in sessions — no debug ports, no separate browser instance.

Feature	Vibe MCP	Playwright MCP	DevTools MCP	Browser MCP
Uses your logged-in browser Playwright supports this via its extension mode, but defaults to launching a separate browser instance
No debug port required Playwright's default mode requires --remote-debugging-port; extension mode avoids this but adds token auth setup
Multi-agent support Multiple AI agents control the same browser simultaneously via relay daemon
Internet-exposed relay Expose your relay to the internet so remote agents can connect to your local browser from anywhere
Google Workspace integration Gmail search/send/draft, Calendar view/create — 7 native tools
Credential vault Secure password manager that never exposes secrets to the LLM
Sub-agent orchestration Spawn sub-agents with isolated context and parallel tool execution
Standalone AI browser Also works as a standalone AI co-pilot directly in your browser
Open source Vibe's MCP server (@vibebrowser/mcp) is open source; the browser extension is not. BrowserMCP is similar
Telemetry to vendor Chrome DevTools MCP sends usage statistics and CrUX API calls to Google by default

Playwright MCP (Microsoft)

Launches a separate Playwright-managed browser. Requires CDP for existing browser connection. 27k GitHub stars.

Chrome DevTools MCP (Google)

Developer debugging tool using Puppeteer + CDP. Launches separate Chrome instance. Sends telemetry to Google by default. 25k GitHub stars.

Browser MCP (Namu)

Chrome extension-based like Vibe. Single agent only. Extension is closed-source. 5.8k GitHub stars.

Two ways to connect: local or remote

Run agents on your machine with the local relay, or connect any agent on the internet to your browser through our public relay server. Both support multiple agents simultaneously.

Local mode — agents on your machine

npx @vibebrowser/mcp

  Claude Code          Cursor           OpenCode
       │                  │                 │
       ▼                  ▼                 ▼
   [vibe-mcp]         [vibe-mcp]        [vibe-mcp]     ← stdio MCP bridges
       │                  │                 │
       └──────────────────┼─────────────────┘
                          │
                   ws://localhost:19888
                          │
                          ▼
                 ┌──────────────────┐
                 │   Local Relay    │  ← auto-spawned daemon
                 │  (localhost only) │
                 └──────────────────┘
                          │
                   ws://localhost:19889
                          │
                          ▼
                 ┌──────────────────┐
                 │  Vibe Extension  │  ← your real Chrome browser
                 └──────────────────┘

Remote mode
New
— agents anywhere on the internet

npx @vibebrowser/mcp --remote <uuid>

  OpenClaw (cloud)     Claude Code (laptop)     Cursor (office)
       │                      │                       │
       ▼                      ▼                       ▼
   [vibe-mcp               [vibe-mcp               [vibe-mcp
    --remote <uuid>]         --remote <uuid>]         --remote <uuid>]
       │                      │                       │
       └──────────────────────┼───────────────────────┘
                              │
                    wss://relay.vibebrowser.app/<uuid>
                              │
                              ▼
                 ┌────────────────────────┐
                 │    Public Relay Server  │  ← hosted by Vibe
                 │  relay.vibebrowser.app  │     UUID-authenticated
                 └────────────────────────┘
                              │
                    wss://relay.vibebrowser.app
                              │
                              ▼
                 ┌──────────────────┐
                 │  Vibe Extension  │  ← your real Chrome browser
                 │   (at home)      │     connects on "Remote" toggle
                 └──────────────────┘

Remote mode setup

In the Vibe extension, go to Settings and enable MCP External Control in Remote mode

This connects your browser to relay.vibebrowser.app and generates a unique UUID

Copy your UUID from the extension settings page

Configure your agent with the --remote flag:

CLI

npx -y @vibebrowser/mcp --remote YOUR_UUID

Share your UUID with any MCP-compatible agent on the internet. They connect to your browser through the relay — no port forwarding, no VPN, no firewall changes needed.

Multi-Agent

Multiple agents connect simultaneously — local or remote, no conflicts

Connect from Anywhere

Any agent on the internet can control your browser — just share your UUID

Authenticated

UUID + secret authentication — only you control who connects

25+ tools across 8 categories

Navigation, interaction, Google Workspace, credential management, sub-agents, and more — all exposed via MCP.

Navigation

navigate_to_urlNavigate to URL and wait for load

navigateBrowser history back / forward / refresh

Tab Management

create_new_tabOpen new tab with optional URL

switch_to_tabSwitch browser focus to tab

set_working_tabSet working tab without focus change

Index-Based Interaction

click_by_indexClick element by [index:score]

fill_by_indexFill form field by index

select_by_indexSelect dropdown option by index

scroll_pageScroll page up or down

media_control_by_indexControl video/audio playback

Advanced Interaction

keypressSend keyboard keys and shortcuts

hover_elementHover to trigger tooltips/menus

Utility

waitWait N seconds

subagentSpawn sub-agent with isolated context

parallelExecute multiple tools in parallel

web_fetchHTTP fetch + text extraction

Visual

take_screenshotJPEG screenshot with resize, grayscale, quality controls

Google Workspace

gmail_searchSearch emails via Gmail API

gmail_get_messageGet full email content

gmail_get_threadGet all messages in thread

gmail_create_draftCreate email draft

gmail_send_messageSend email

calendar_viewView upcoming events

calendar_createCreate calendar event

Credential Management

secrets_managerList/read saved credentials

typein_secretFill form from vault (hidden from LLM)

Set up in under 2 minutes

Install Extension

Install the Vibe AI Browser extension and enable MCP External Control in Settings.

Configure Your Agent

Add the MCP server config to your AI agent. Pick your agent below — copy, paste, done.

Configuration for every agent

Click an agent to see the config. Copy, paste, done.

CLI

claude mcp add --transport stdio vibe -- npx -y @vibebrowser/mcp

Or add to project-level .mcp.json

Markdown-indexed pages, not raw DOM

Instead of dumping raw accessibility trees or DOM snapshots, Vibe extracts page content as clean markdown. Interactive elements get [index:score] labels that agents use to click, fill, and interact.

Lower token usage

Markdown is 3-5x smaller than raw DOM or accessibility trees

Scored interactions

Elements scored by relevance — agents focus on what matters

Automatic delivery

Page content sent before each agent turn — no tool call needed

page content (auto)

# GitHub - VibeTechnologies/vibe-mcp

MCP server for browser automation.

## Quick Start

[1:0.9] Install extension
[2:0.8] View documentation
[3:0.7] Star repository

## Features
- Multi-agent support
- 25+ browser tools
- Google Workspace integration

[4:0.6] Sign in
[5:0.5] Fork repository
[6:0.3] Watch

Frequently asked questions

Ready to connect your AI agent to your browser?

Install the extension, add one config block, and start automating. Free, with an open source MCP server.

Questions? [email protected] · GitHub · npm

Morningstar Schwab research automation Private legal research automation LinkedIn recruiter automation All use cases

Control Your Browser from Any AI Agent|