Chrome MCP vs Real Browser MCP
A side-by-side look at the Chrome MCP and Real Browser MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chrome MCP for browser automation work as a local process; choose Real Browser MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chrome MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CHROME_MCP_TOKEN, CHROME_MCP_EXTENSION_DIR.
Choose Real Browser MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
browser_navigate, browser_click, browser_type.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 47/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CHROME_MCP_TOKENCHROME_MCP_EXTENSION_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 54 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View Chrome MCP | View Real Browser MCP |
Tools & capabilities
Chrome MCP tools
No tool names declared yet. Check the project README from the listing page.
Real Browser MCP tools 18
browser_navigateNavigate to a URL in the active browser tabbrowser_clickClick an element on the page using a ref from snapshot or a CSS selectorbrowser_typeType text into an input elementbrowser_scrollScroll the page or an element. Supports pixel offsets, scrolling to elements, and named positions (top/bottom). Works with virtual scroll containers used by social media sites.browser_press_keyPress a keyboard key or combination (Enter, Escape, Tab, ArrowDown, etc). Supports modifiers like Ctrl+A, Cmd+C.browser_waitWait for a condition: element to appear, element to disappear, or a fixed delay. Useful for SPAs and dynamic content.browser_snapshotGet an accessibility tree snapshot of the page. Returns element refs you can use with click, type, and other tools. Use compact mode (default) for smaller output - only interactive elements.browser_screenshotCapture a screenshot of the visible page areabrowser_consoleRead console messages (log, warn, error) from the browserbrowser_networkRead network requests made by the page. Filter by URL pattern.browser_tabsManage browser tabs: list, create, close, or focusbrowser_findFind elements on the page using natural language (e.g. "login button", "search input"). Returns refs you can use with click/type.- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chrome MCP
{
"mcpServers": {
"chrome-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-browser-extension@latest"
],
"env": {
"CHROME_MCP_TOKEN": "YOUR_CHROME_MCP_TOKEN_HERE",
"CHROME_MCP_EXTENSION_DIR": "YOUR_CHROME_MCP_EXTENSION_DIR_HERE"
}
}
}
}
Real Browser MCP
{
"mcpServers": {
"ofershap-real-browser-mcp": {
"command": "npx",
"args": [
"-y",
"real-browser-mcp"
]
}
}
}
Frequently asked questions
Chrome MCP is categorized under Browser Automation and uses a local stdio subprocess. Real Browser MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Chrome MCP for browser automation work and Real Browser MCP for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Chrome MCP has no declared pricing — check the project's own site. Real Browser MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chrome-mcp and ofershap-real-browser-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chrome MCP has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Real Browser MCP has 67/100 (Great) with 3 views, 0 installs and 54 GitHub stars.
