Vibe Browser works with any AI agent

One MCP server — @vibebrowser/mcp — gives Claude Desktop, Claude Code, OpenAI Codex CLI, Cursor, VS Code Copilot, Windsurf, Gemini CLI, and OpenCode control of your real, logged-in Chrome. Not a headless clone. The browser you already use.

Last updated: August 2026

What is Vibe MCP?

Vibe MCP is a Model Context Protocol server that gives any AI agent control of your real Chrome browser. Install the Vibe extension, add one entry to your agent's MCP config, and the agent can navigate, click, fill forms, screenshot, and read pages — including sites you are already logged into. Multiple agents can share one browser.

Using Claude or ChatGPT in a browser tab?

Those cannot run a local MCP server, so skip the config files below — they take a single connector URL instead. Both paths are documented end to end, including the exact click path, what “connected” looks like, and a prompt you can run to prove it works. Neither needs domain verification or an allowlist, and there is no consent screen: you paste https://relay.api.vibebrowser.app/mcp/<your-routing-uuid> — the URL you copy from the Vibe extension — and that is the whole setup. Verified on Claude on the web. On ChatGPT it needs a paid plan, because Plugins → Create app silently no-ops on a free account, so the URL field never appears. That URL is a bearer credential for your browser: do not share it, and regenerate it in the extension if it leaks.

Supported AI agents

Every client below is documented in the @vibebrowser/mcp README. The config snippets are the real ones — copy, paste, restart.

Vibe MCP connects Claude Desktop to your real Chrome browser through the Model Context Protocol. Add one entry to claude_desktop_config.json, install the Vibe extension, and Claude can navigate, click, fill forms, read pages, and manage tabs in the browser where you are already signed in.

claude_desktop_config.jsonjson
{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "@vibebrowser/mcp"]
    }
  }
}
Full Claude Desktop setup guide →

Claude Code

Anthropic

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.

terminalbash
claude mcp add vibe -- npx -y @vibebrowser/mcp
Full Claude Code setup guide →

Vibe MCP adds browser tools to OpenAI Codex CLI over the Model Context Protocol. Add the @vibebrowser/mcp server to your Codex configuration and Codex can navigate, click, type, scroll, screenshot, and extract content from your real Chrome, including pages that require a login.

~/.codex/config.tomltoml
[mcp_servers.vibe]
command = "npx"
args = ["-y", "@vibebrowser/mcp"]
Full OpenAI Codex CLI setup guide →

The ChatGPT desktop app supports MCP servers. Add @vibebrowser/mcp as a STDIO server under Settings → MCP servers, and ChatGPT can navigate, click, type, scroll, screenshot, and extract content from your real Chrome — including pages behind a login. The desktop app, Codex CLI, and Codex IDE extension share one config at ~/.codex/config.toml.

Terminal (writes ~/.codex/config.toml, shared with the desktop app)bash
codex mcp add vibe -- npx -y @vibebrowser/mcp
Full ChatGPT desktop app setup guide →

Claude supports custom connectors backed by a remote MCP server. Open Settings → Connectors → Add → Add custom connector and paste your Vibe connector URL, https://relay.api.vibebrowser.app/mcp/ followed by the routing UUID from the extension. Claude can then navigate, click, type, scroll, screenshot, and read your real Chrome — including pages behind a login. Because the connector is brokered by your Claude account, it works in Cowork and on mobile, not just Claude Desktop.

Vibe extension → Settings → Agent connection URLurl
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
Full Claude (web, Cowork & mobile) setup guide →

ChatGPT supports custom apps backed by a remote MCP server. Go to chatgpt.com/plugins, click Add, then Add custom MCP server, and paste your Vibe connector URL, https://relay.api.vibebrowser.app/mcp/ followed by the routing UUID from the extension. Set Authentication to No Auth — the URL itself is the credential. ChatGPT can then navigate, click, type, scroll, screenshot, and read your real Chrome, including pages behind a login, with no local MCP server running. This is the direct per-user URL, and it is the path we verified end to end here — on a paid plan.

Vibe extension → Settings → Agent connection URLurl
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
Full ChatGPT connectors setup guide →

Cursor

Anysphere

Vibe MCP gives Cursor browser tools through the Model Context Protocol. Add the "vibe" server in Cursor Settings or ~/.cursor/mcp.json, install the Vibe Chrome extension, and Cursor can navigate, click, fill forms, screenshot, and read page content in the browser you are already signed into.

~/.cursor/mcp.jsonjson
{
  "vibe": {
    "command": "npx",
    "args": ["-y", "@vibebrowser/mcp"]
  }
}
Full Cursor setup guide →

VS Code (GitHub Copilot)

Microsoft / GitHub

Vibe MCP adds browser tools to GitHub Copilot Chat in VS Code. Add the "vibe" server under github.copilot.chat.mcpServers in settings.json, install the Vibe Chrome extension, and Copilot can navigate, click, type, screenshot, and read pages in your real Chrome session.

VS Code settings.jsonjson
{
  "github.copilot.chat.mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "@vibebrowser/mcp"]
    }
  }
}
Full VS Code (GitHub Copilot) setup guide →

Windsurf

Codeium

Vibe MCP connects Windsurf to your real Chrome browser. Add the "vibe" server to ~/.codeium/windsurf/mcp_config.json, install the Vibe extension, and Windsurf can navigate, click, fill forms, screenshot, and extract content from pages you are already logged into.

~/.codeium/windsurf/mcp_config.jsonjson
{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "@vibebrowser/mcp"]
    }
  }
}
Full Windsurf setup guide →

Vibe MCP gives Gemini CLI browser tools through the Model Context Protocol. Add the "vibe" server to ~/.gemini/settings.json, install the Vibe Chrome extension, and Gemini can navigate, click, type, screenshot, and read content from your real Chrome session.

~/.gemini/settings.jsonjson
{
  "mcpServers": {
    "vibe": {
      "command": "npx",
      "args": ["-y", "@vibebrowser/mcp"]
    }
  }
}
Full Gemini CLI setup guide →

OpenCode

OpenCode

Vibe MCP connects OpenCode to your real Chrome browser. Add the "vibe" server under mcp.servers in .opencode/config.json, install the Vibe extension, and OpenCode can navigate, click, fill forms, screenshot, and read content from pages you are already logged into.

.opencode/config.jsonjson
{
  "mcp": {
    "servers": {
      "vibe": {
        "command": "npx",
        "args": ["-y", "@vibebrowser/mcp"]
      }
    }
  }
}
Full OpenCode setup guide →

Grok can connect to outside tools with custom connectors. Open grok.com/connectors, choose New Connector, then Custom, and paste your Vibe URL: https://relay.api.vibebrowser.app/mcp/ plus your routing UUID from the Vibe extension. Grok can then open pages, click, type, and read your real Chrome — even on sites where you are logged in.

Vibe extension → Settings → Agent connection URLurl
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
Full Grok & Grok Bots setup guide →

Dots

OpenAI

Dots are always-on agents inside ChatGPT, launched by OpenAI on September 29, 2026. A dot runs on its own cloud computer and uses the same apps and connectors you add in ChatGPT — there is no separate Dots connector setup. So the whole setup is the ChatGPT one: add Vibe at chatgpt.com/plugins as a custom MCP server with your connector URL, and your dot can open, read, and act on pages in your real Chrome. Dots need a ChatGPT Pro or Business Premium plan.

Vibe extension → Settings → Agent connection URLurl
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
Full Dots setup guide →

Claude for Chrome, ChatGPT for Chrome and Muse for Chrome each put one vendor’s agent in your browser. VibeBrowser is different: it is one browser that any agent can drive. Connect Muse to it from chat — copy your full MCP connector URL from the Vibe extension (Settings → AI Agent Control, Connection mode Remote) and send Muse the message on this page with your URL in it. The session ID is already in the URL path, so the connector needs no API key, no authorization header and no other secret. Muse adds Vibe Browser as a custom connector; it then lives in the Muse app under Settings → Connectors → Custom connectors, and Muse can open, read, and act on pages in your real Chrome. The same browser also connects to Claude, ChatGPT, Codex and other MCP agents, runs local on-device models, and never locks you to one AI vendor.

Paste into a Muse chatbash
Add a custom connector named "Vibe Browser" using this MCP server URL: https://relay.api.vibebrowser.app/mcp/<session-id> — the session ID is already in the URL path, so this connector needs no API key, no authorization header, and no other secret. Do not ask me for a credential. Once it is connected, list my open browser tabs to check it works, and do not click or change anything yet.
Full Muse by Meta setup guide →

OpenClaw

OpenClaw

OpenClaw connects to MCP servers from its config file. Add a "vibe" entry under mcpServers in ~/.openclaw/openclaw.json with your Vibe connector URL — https://relay.api.vibebrowser.app/mcp/ plus your routing UUID from the extension — and restart OpenClaw. Its browser tools load on startup, and your agent can open, read, click, and type in your real Chrome, logged-in pages included.

Vibe extension → Settings → Agent connection URLurl
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
Full OpenClaw setup guide →

Hermes

Hermes Agent

Hermes connects to MCP servers from ~/.hermes/config.yaml. Add a "vibe" entry under mcp_servers with your Vibe connector URL — https://relay.api.vibebrowser.app/mcp/ plus your routing UUID from the extension — then restart Hermes (or run /reload-mcp in chat). Check it with "hermes mcp test vibe". Hermes can then open, read, click, and type in your real Chrome, logged-in pages included.

Vibe extension → Settings → Agent connection URLurl
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
Full Hermes setup guide →

Tools every agent 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

Vibe MCP vs Playwright MCP vs BrowserMCP

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

Security

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.

What the relay carries, what it logs, how long it keeps it, and how to revoke access is documented in our Privacy Policy.

Frequently asked questions

Which AI agents work with Vibe Browser?
Vibe Browser works with any MCP client. Documented setups exist for Claude Desktop, Claude Code, OpenAI Codex CLI, Cursor, VS Code (GitHub Copilot), Windsurf, Gemini CLI, and OpenCode. All of them use the same @vibebrowser/mcp server.
Can two AI agents control the same browser at once?
Yes. Vibe MCP is the only browser automation server built for multi-agent use. A local relay daemon multiplexes connections, so Claude Desktop, Cursor, and a CLI agent can all drive the same Chrome window without port conflicts.
Do I need a separate browser or a cloud browser?
No. Vibe runs as a Chrome extension inside the browser you already use, so agents act on your existing tabs, cookies, and logged-in sessions instead of a clean headless profile.
How is Vibe different from Playwright MCP or BrowserMCP?
Playwright MCP and BrowserMCP launch an isolated browser with no sessions and fail when a second agent connects. Vibe uses your real browser profile, keeps logged-in sessions, and supports multiple agents simultaneously.
Is my browsing data sent anywhere?
No. The MCP server and relay daemon run locally on your machine. Page content is only shared with the AI agent you connected.

Get started

Install the Vibe extension, then pick your agent above and paste the config.