
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
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.
Installation
In SourceWeft
- Open Browser Mcp Cdp in the dashboard and add it to a workspace.
- 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:
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
Or add manually to ~/.claude.json / Claude Desktop config:
Requires Node 18+ and Google Chrome installed.
Tools
Environment variables
How it works
- First MCP client connection spawns a broker subprocess (detached).
- Broker copies your Chrome profile's cookies/local storage/login data to a temp dir.
- Broker launches Chrome with
--user-data-dir=<temp>and--remote-debugging-port. - Subsequent MCP clients connect to the same broker over a Unix socket → they share one Chrome.
- Broker exits after
BROKER_IDLE_TIMEOUT_MSof 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
0Version history
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