Log inSubmit server
Browser MCP Cdp logo

Browser MCP Cdp

Local Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Browser MCP Cdp

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": {
    "browser-mcp-cdp": {
      "command": "npx",
      "args": [
        "-y",
        "browser-mcp-cdp"
      ]
    }
  }
}

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

Automated check passed— started and listed 13 tools correctly (21d ago).

Overview

Tools13

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

Verified live~908 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 Today

Recent health check succeeded.

12/12 checks healthy over the last 61d

What it can do

From the 13 tools this server returned when we ran it.

Runs commands · 1Makes network requests · 4Read-only tools · 12
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age178 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · browser-mcp-cdp (npm)

Adoption & maintenance

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

npm downloads156Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed13Callable tools this server registers over MCP.
Directory activity13 viewsConfig copies, upvotes, and views on AllMCPs.

From the project README

browser-mcp-cdp

A Model Context Protocol (MCP) server that drives your real local Chrome via the Chrome DevTools Protocol. Designed for agents that need access to your logged-in sessions (Gmail, internal dashboards, banking, etc.) without uploading credentials to a cloud service.

Why another browser MCP?

Different tradeoffs from the alternatives:

browser-mcp-cdpPlaywright MCPChrome DevTools MCP
BrowserYour local ChromeManaged Playwright ChromiumYour local Chrome
Login state✅ Snapshot of your profile (cookies, logins, IndexedDB)❌ Fresh profile✅ Real profile (modifies it)
Profile isolation✅ Copy-on-start, real profile untouchedN/A⚠️ Direct attach
Multi-client✅ Shared broker across MCP clients❌ Per-client❌ Per-client
DependenciesNode only (no Playwright download)Playwright + browsersNode only

The profile snapshot pattern means you can ask an agent to "check my email" — it sees your Gmail logged in — but the agent's actions never modify your real Chrome profile. Each session gets a disposable copy.

Install

Terminal
claude mcp add browser -- npx -y browser-mcp-cdp

Or add manually to ~/.claude.json / Claude Desktop config:

config.json
{
  "mcpServers": {
    "browser": {
      "command": "npx",
      "args": ["-y", "browser-mcp-cdp"]
    }
  }
}

Requires Node 18+ and Google Chrome installed.

Tools

ToolPurpose
browser_navigateLoad a URL, return final URL + title
browser_evaluateRun JS in the page, return result
browser_screenshotPNG of current page
browser_clickClick via CSS selector
browser_click_atClick at pixel coordinates (pierces iframes / overlays)
browser_fillSet value on input/textarea/select
browser_wait_forWait for a selector to appear
browser_get_urlCurrent URL
browser_get_textVisible text of page or element
browser_get_htmlouterHTML of page or element
browser_scrollScroll by (x, y) pixels
browser_tabsList open tabs
browser_new_tabOpen a new tab

Environment variables

VarDefault
BROWSER_MCP_CHROME_PATHAuto-detected per OS
BROWSER_MCP_CHROME_PROFILE_ROOTOS-standard Chrome profile dir
BROWSER_MCP_BROKER_SOCKET_PATH~/.browser-mcp/broker.sock
BROWSER_MCP_BROKER_LOCK_PATH~/.browser-mcp/broker.lock
BROWSER_MCP_BROKER_IDLE_TIMEOUT_MS600000 (10 min)

How it works

  1. First MCP client connection spawns a broker subprocess (detached).
  2. Broker copies your Chrome profile's cookies/local storage/login data to a temp dir.
  3. Broker launches Chrome with --user-data-dir=<temp> and --remote-debugging-port.
  4. Subsequent MCP clients connect to the same broker over a Unix socket → they share one Chrome.
  5. Broker exits after BROKER_IDLE_TIMEOUT_MS of no activity; temp profile is deleted.

Security

This server lets an LLM execute arbitrary JavaScript in a browser that is logged into your accounts. Only use with models and prompts you trust. Profile snapshotting limits damage (no persistent mutations to your real Chrome), but the agent can read cookies, session tokens, and any data visible to logged-in you for the duration of the session.

License

MIT

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 Browser MCP Cdp

browser-mcp-cdp is an MCP server that drives your local Google Chrome through the Chrome DevTools Protocol. It creates a disposable snapshot of your Chrome profile, preserving access to logged-in sessions while leaving the original profile untouched. A shared broker lets multiple MCP clients use the same browser session, with Node.js as the main dependency.

Install browser-mcp-cdp with Claude using `claude mcp add browser -- npx -y browser-mcp-cdp`, or add it to your MCP configuration with the `npx` command and package name. Node.js 18 or newer and Google Chrome are required.

No, browser-mcp-cdp copies your Chrome profile to a temporary directory and launches the agent’s browser from that snapshot. This preserves cookies, login state, and IndexedDB access while keeping the original Chrome profile unchanged; the temporary profile is deleted when the broker exits.

Yes, multiple MCP clients can share one Chrome session through the broker. The first client connection starts a detached broker, and subsequent clients connect to it over a Unix socket until it exits after the configured idle timeout.

browser-mcp-cdp provides tools for navigation, JavaScript evaluation, screenshots, clicking, form filling, waiting for selectors, reading URLs, visible text, and HTML, scrolling, listing tabs, and opening new tabs.

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 PreviewBrowser MCP Cdp AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/browser-mcp-cdp?style=directory)](https://allmcps.com/mcp/browser-mcp-cdp)
HTML Embed
<a href="https://allmcps.com/mcp/browser-mcp-cdp"><img src="https://allmcps.com/api/badge/browser-mcp-cdp?style=directory" alt="Browser MCP Cdp on AllMCPs" /></a>