Browser Mcp Cdp

io.github.zhiqi-liPublished by GitHub account zhiqi-liv0.1.2Updated Oct 27, 2026

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

Overview

AI-generated overview

MCP server that drives your real local Chrome over the DevTools Protocol using a disposable copy of your Chrome profile, so agents see your logged-in sessions.

What you can do
  • Navigate to URLs and read the final URL, title, visible text or HTML of a page or element
  • Run JavaScript in the page and get the result back
  • Take PNG screenshots and scroll the page by pixel offsets
  • Click by CSS selector or by pixel coordinates, fill inputs, textareas and selects, and wait for selectors
  • List open tabs and open new tabs
  • Share one Chrome instance across several MCP clients through a detached broker process
When to use it
Useful when an agent needs to work inside sites you are already signed in to, such as webmail, internal dashboards or banking portals, without handing credentials to a cloud browser. Also fits setups where several MCP clients should share a single browser session.
Requirements
Runs as a local process via npx (npm package browser-mcp-cdp); needs Node 18+ and Google Chrome installed. Optional environment variables set the Chrome path, profile root, broker socket and lock paths, and broker idle timeout. Desktop only.
Before you install
The agent can execute arbitrary JavaScript in a browser logged into your accounts and can read cookies, session tokens and any data visible to you during the session. Only use with models and prompts you trust. Profile snapshotting avoids persistent changes to your real Chrome profile, but the temporary copy is deleted only when the broker exits after its idle timeout.

Installation

In SourceWeft

  1. Open Browser Mcp Cdp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

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

Or add manually to ~/.claude.json / Claude Desktop 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

Source: README.md at commit 0cf6e0b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts