Log inSubmit server
Real Browser MCP logo

Real Browser MCP

by ofershap

Controls an existing Chrome session through MCP, preserving logged-in tabs, cookies, and SSO access.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Real Browser MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ofershap-real-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "real-browser-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

ofershap/real-browser-mcp connects an MCP client to an already-running Chrome browser through a local server, a Chrome extension, and a localhost WebSocket. Agents can inspect pages, navigate, interact with controls, read browser diagnostics, manage tabs, and execute page JavaScript without launching a separate browser profile. It is suited to verifying fixes in authenticated staging environments or working with the tab and session already open on a developer’s machine. For repeatable clean-browser CI runs, a dedicated automation setup such as Playwright is the better fit.

Use cases

  • Verify a fix in an authenticated staging tab
  • Inspect a page behind SSO without re-authenticating
  • Interact with an existing Chrome session during development
  • Read console and network activity from a live page

Key features

  • Controls an existing Chrome session through a local extension
  • Preserves browser cookies, SSO state, and open tabs
  • Provides accessibility snapshots and screenshots
  • Supports clicks, typing, scrolling, keys, dropdowns, and dialogs
  • Reads console messages and filtered network requests
  • Runs JavaScript in the current page

Tools18

What Real Browser MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/20 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · real-browser-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars58Stargazers on the source repository.
npm downloads504Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed18Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Real Browser MCP works

What ofershap/real-browser-mcp does

ofershap/real-browser-mcp gives an AI agent access to the user’s active Chrome session through MCP. Instead of creating a fresh Chromium instance, it operates through a Chrome extension installed in the user’s browser. This lets the agent work with tabs that already contain cookies, SSO state, staging access, and other local session context.

The design targets development workflows where a developer has reproduced a problem or opened a page manually and wants an agent to inspect or verify it. The browser remains local, and the extension carries out the requested actions in Chrome.

How it works

The setup has two cooperating parts. An MCP server runs locally and communicates with the selected AI client. A Chrome extension runs inside Chrome and executes browser operations. The two components communicate over a localhost WebSocket.

The agent can first request an accessibility snapshot, receive references for interactive elements, and then use those references for actions such as clicking or typing. It can also use screenshots, page text, natural-language element lookup, or JavaScript evaluation when a snapshot is not the right representation. Waiting tools support dynamic pages and single-page applications.

Setup and configuration

Add the MCP server to an MCP-compatible client with a command such as npx -y real-browser-mcp. Cursor provides a one-click installation option, while Claude Desktop and Windsurf use their normal MCP configuration locations. The server can also be added manually using an MCP configuration entry with npx as the command.

Install the Real Browser MCP extension from the Chrome Web Store, or clone the repository and load its extension/ directory as an unpacked extension from chrome://extensions with Developer mode enabled. The extension icon indicates the connection state: green means connected and gray means it is waiting for the server.

Optional setup commands add workflow guidance for agents. npx real-browser-mcp --setup cursor installs Cursor rules and a /check-browser command. npx real-browser-mcp --setup claude adds an AGENTS.md file for Claude Code. These files encourage a snapshot-first process and describe when to use screenshots, dropdown handling, and verification steps.

Tools and capabilities

The MCP toolset includes:

  • browser_navigate for changing the active tab’s URL.
  • browser_snapshot, browser_screenshot, and browser_text for inspecting visible content, structure, and page text.
  • browser_find for locating elements with a natural-language description.
  • browser_click, browser_click_text, browser_type, browser_hover, and browser_select for interacting with controls, including React overlays and dropdowns.
  • browser_scroll for page or element scrolling, including virtual scroll containers and named positions.
  • browser_press_key for keys and modifier combinations such as Ctrl+A or Cmd+C.
  • browser_wait for delays or waiting until an element appears or disappears.
  • browser_tabs for listing, creating, closing, and focusing tabs.
  • browser_console and browser_network for reading console output and filtered network requests.
  • browser_evaluate for running JavaScript in the page.
  • browser_handle_dialog for accepting, dismissing, or responding to JavaScript dialogs.

Limitations and notes

This approach depends on Chrome and the installed extension being available on the same machine as the local MCP server. It is intended for interacting with an existing, authenticated browser rather than providing an isolated browser for parallel or repeatable CI jobs. It also does not use a hosted browser or a newly created profile. The project is released under the MIT license.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Real Browser MCP

ofershap/real-browser-mcp is an MCP server that connects AI clients to the user’s existing Chrome session through a local Chrome extension and WebSocket. Its main tools navigate pages, inspect snapshots and screenshots, click and type, manage tabs, read console and network data, and execute page JavaScript.

Install the MCP package in your client with `npx -y real-browser-mcp`, then install the Chrome extension from the Web Store. You can instead clone the repository and load its `extension/` folder as an unpacked extension from `chrome://extensions` with Developer mode enabled.

Yes, ofershap/real-browser-mcp works with Cursor. Cursor supports a one-click MCP installation or a manual configuration using `npx -y real-browser-mcp`. The repository also provides `npx real-browser-mcp --setup cursor` for optional rules and a `/check-browser` command.

Yes, it operates through the Chrome session already open on your machine, so existing cookies, SSO state, and authenticated tabs can be used. The extension must be connected to the local MCP server before the agent can interact with that browser.

No, it is aimed at live verification in a developer’s existing Chrome session rather than repeatable parallel CI runs. Its workflow depends on a local browser and extension; isolated CI automation is better handled with a dedicated browser automation setup.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewReal Browser MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ofershap-real-browser-mcp?style=directory)](https://allmcps.com/mcp/ofershap-real-browser-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ofershap-real-browser-mcp"><img src="https://allmcps.com/api/badge/ofershap-real-browser-mcp?style=directory" alt="Real Browser MCP on AllMCPs" /></a>