MCP Directory

How to add Real Browser MCP to Claude Desktop

Give AI agents control of your real Chrome browser with existing sessions, cookies, and logins. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 33★ · stdio · no auth

Claude Desktop config for Real Browser MCP

npx -y real-browser-mcp
{
  "mcpServers": {
    "real-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "real-browser-mcp"
      ]
    }
  }
}

Setup steps

  1. 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
  2. 2Paste the Real Browser MCP config below under the top-level "mcpServers" key.
  3. 3Fill in any placeholder secrets (API keys, paths) in the snippet.
  4. 4Save the file, then fully quit and reopen Claude Desktop.
  5. 5Open a chat and confirm Real Browser MCP's tools appear under the 🔌 tools menu.

Before you start

  • Node.js with npx available (for the MCP server)
  • Google Chrome with the Real Browser MCP extension installed (from the Chrome Web Store or loaded unpacked from the extension/ folder)
  • An MCP-compatible client such as Cursor, Claude Desktop, Claude Code, Windsurf, or Cline

What Real Browser MCP can do in Claude Desktop

browser_snapshot

Capture the accessibility tree with element refs; compact mode (default) returns only interactive elements.

browser_screenshot

Capture what is currently on screen.

browser_text

Extract raw text from the page or a specific element.

browser_find

Query elements by CSS selector.

browser_click

Click an element by ref or CSS selector.

browser_click_text

Click by visible text; works through React portals and overlays.

browser_type

Type into inputs and contenteditable fields.

browser_press_key

Send key combos such as Enter, Escape, or Ctrl+A.

Security

Everything stays local: the MCP server and Chrome extension communicate over WebSocket on localhost only. No cloud component, no analytics, no telemetry. Because the extension runs inside your actual Chrome, the agent inherits all of your logged-in sessions and can act on any site you are authenticated to, so grant access only to agents you trust.

Real Browser MCP + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Real Browser MCP config there under the "mcpServers" key and restart the client.

Is Real Browser MCP safe to use with Claude Desktop?

Everything stays local: the MCP server and Chrome extension communicate over WebSocket on localhost only. No cloud component, no analytics, no telemetry. Because the extension runs inside your actual Chrome, the agent inherits all of your logged-in sessions and can act on any site you are authenticated to, so grant access only to agents you trust.

Does it work with my logged-in sessions?

Yes, that is the whole point. The extension runs inside your actual Chrome with the same cookies, sessions, and local storage, so no re-authentication is needed.

Does it send data anywhere?

No. The MCP server and extension talk over WebSocket on localhost. Nothing leaves your machine, and there is no analytics, telemetry, or cloud component.

Which AI clients work?

Any MCP-compatible client, including Cursor, Claude Desktop, Claude Code, Windsurf, and Cline.

View repo Full Real Browser MCP page