Add it to Claude Code
claude mcp add real-browser-mcp -- npx -y real-browser-mcpMake your agent remember this setup
real-browser-mcp's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Uses your existing browser sessions, logins, and cookies
- Works behind corporate SSO
- Provides 18 tools for browser interaction
- Compatible with Cursor, Claude Desktop, and Windsurf
- Includes a Chrome extension for real-time browser control
Tools 4
navigateNavigate the browser to a specific URLclickClick an element on the current pagetypeType text into an input fieldsnapshotTake a screenshot and get the accessibility tree of the current pageTry it
Original README from ofershap/real-browser-mcp
<strong>The missing piece in AI coding: your agent can now see your REAL browser.</strong>
You ship a fix. Your agent says "done, please verify." You alt-tab to Chrome, navigate to the page, log in, click around, find the bug.
Your agent just wrote the code. It could also verify it. It already has your browser open right there. It just can't see it.
Now it can.
Quick Start
Two parts:
- MCP server - runs on your machine, talks to your AI agent
- Chrome extension - sits in your browser, executes the commands
1. Add the MCP server
Cursor (one click):
Or add manually in Cursor Settings > MCP > "Add new MCP server":
{
"mcpServers": {
"real-browser": {
"command": "npx",
"args": ["-y", "real-browser-mcp"]
}
}
}
Claude Desktop: Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Add the same JSON block.
Windsurf: Settings > MCP. Same config.
Any MCP-compatible client works.
</details>2. Install the Chrome extension
Or load from source:
git clone https://github.com/ofershap/real-browser-mcp.git
- Open
chrome://extensionsand enable Developer mode (toggle in the top right) - Click Load unpacked and select the
extension/folder from the cloned repo
Click the Real Browser MCP icon in your toolbar.
Green dot = connected. Gray = waiting for server.
Done. Your agent can see your browser.
How Others Compare
| Real Browser MCP | Playwright MCP | Chrome DevTools MCP | |
|---|---|---|---|
| Uses your existing browser | Yes | No, launches new | Partial, needs debug port |
| Sessions and cookies | Already there | Fresh profile | Manual setup |
| Works behind corporate SSO | Yes | No | Depends |
| Setup | Extension + MCP config | Headless browser | Chrome with --remote-debugging-port |
🧠 Teach Your Agent
The agent can use all 18 tools out of the box, but it works better when it knows when and how to chain them. A config file teaches the right workflow - snapshot first, then act, then verify.
Run one command:
npx real-browser-mcp --setup cursor
This installs:
- `~/.curso