MCP Directory

Real Browser MCP

Give AI agents control of your real Chrome browser with existing sessions, cookies, and logins.

Unverified
stdio (local)
No auth
TypeScript
View repo 33 npm

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run
npx -y real-browser-mcp

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

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

About Real Browser MCP

Real Browser MCP is a two-part tool: an MCP server (npm package real-browser-mcp) that runs on your machine and talks to your AI agent, and a Chrome extension (Manifest V3) that sits in your browser and executes the commands. The two communicate over a localhost WebSocket (default port 7225). Because the extension lives inside your real Chrome, the agent operates with your existing cookies, sessions, and logins already loaded, including pages behind corporate SSO. It exposes 18 tools across See, Interact, Navigate, and Debug groups, and ships pre-built agent rules for Cursor and Claude Code that teach a snapshot-first workflow. Connection drops are handled automatically with exponential backoff, ping/pong health checks, and per-tool timeouts.

Tools & capabilities (18)

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.

browser_scroll

Scroll pages and virtual containers.

browser_hover

Hover to trigger tooltips and dropdowns.

browser_select

Pick an option from native <select> dropdowns.

browser_wait

Wait for elements to appear or disappear.

browser_navigate

Go to a URL in the active tab.

browser_tabs

List, create, close, or focus tabs.

browser_console

Read console output (log, warn, error).

browser_network

Inspect XHR/fetch requests with status codes.

browser_evaluate

Run JavaScript via the Chrome DevTools Protocol.

browser_handle_dialog

Handle alert, confirm, and prompt dialogs.

What this server can do

Real Browser MCP provides tools for these capabilities — tap one to see every MCP server that does the same:

Automate a browser

When to use it

  • Let the agent verify its own code fixes by navigating and clicking through the real, logged-in app
  • Automate workflows on sites behind corporate SSO without replaying login flows
  • Debug front-end issues by reading console errors and network requests from the live page
  • Drive multi-tab browsing and form filling using your existing browser state
  • Run JavaScript against the current page via the DevTools Protocol for inspection or scripting

Security notes

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 FAQ

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.

Can I use it with multiple Chrome profiles?

Yes. Run two MCP server instances on different ports (set WS_PORT for the second) and update the port in each extension popup to match.

How is this different from Playwright MCP or browser-use?

Those launch a brand-new browser with no state, cookies, or sessions, so you replay the full login flow every time. Real Browser MCP connects to the browser you already have open with everything loaded.

#browser-automation#chrome-extension#chrome#real-browser#sessions#cursor#claude#devtools-protocol#accessibility-tree

Alternatives to Real Browser MCP

Compare all alternatives →
Browser MCP
Browser Automation
6.7k

Automate your existing browser with AI using your real profile, logged-in sessions, and stealth fingerprint.

Unverified
stdio (local)
No auth
Stale
TypeScript
13 tools
Updated 1 year agoRepo
Bright Data MCP
Browser Automation
5.0k

All-in-one web access MCP — Web Unlocker, SERP, Scraper API, and a cloud Scraping Browser.

Verified
stdio (local)
API key
JavaScript
12 tools
Updated 26 days agoRepo
Peekaboo
Browser Automation
4.8k

macOS screen capture, AI visual analysis, and full GUI automation for AI agents.

Unverified
stdio (local)
API key
Swift
28 tools
Updated 3 days agoRepo

Compare Real Browser MCP with:

vs Browser MCPvs Bright Data MCPvs Peekaboovs Playwright MCP (ExecuteAutomation)