Browser Cdp MCP server
io.github.zhiqi-li/browser-mcp-cdp·v0.1.2Local Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support
0 stars42 downloads/wk
Reviews
Write oneNobody has reviewed Browser Cdp yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Browser Cdp tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
browser_screenshotCapture a screenshot of the current page. Returns a PNG image.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan13 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 158 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Browser Cdp compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 58% of 866 Scraping and browsing servers
- Tools
- 1
- the typical Scraping and browsing server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 42
- more than 25% of 309 Scraping and browsing servers with a package
What its tools let an agent do: 1 read
Install Browser Cdp in Claude Code, Cursor or VS Code
Runs npx -y browser-mcp-cdp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add browser-mcp-cdp -- npx -y browser-mcp-cdp
What the publisher says
From the Browser Cdp repository's README, as published. We do not edit it. Read it on GitHub
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
claude mcp add browser -- npx -y browser-mcp-cdpOr add manually to ~/.claude.json / Claude Desktop config:
{
"mcpServers": {
"browser": {
"command": "npx",
"args": ["-y", "browser-mcp-cdp"]
}
}
}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= and --remote-debugging-port.
- Subsequent MCP clients connect to the same broker over a Unix socket → they share one Chrome.
- Broker exits after BROKERIDLETIMEOUT_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
Nothing above is checked by us. What we check is on the safety report.
Browser Cdp: common questions
- Is Browser Cdp MCP server safe?
- Mostly: it is graded B (82/100). Read the Browser Cdp safety report
- How do I install Browser Cdp?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Browser Cdp need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Browser Cdp maintained?
- The last commit was 195 days ago (2026-04-23). The latest release is v0.1.2.
- What can I use instead of Browser Cdp?
- Servers from other publishers that do the same job: Browser Gateway MCP server, Public Browser MCP server and nodriver — Chrome browser automation MCP server.
- How does Browser Cdp compare with other Scraping and browsing MCP servers?
- safety score 82/100 (higher than 58% of 866 Scraping and browsing servers); tools 1 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Browser Cdp
Same job from other publishers: the closest match first, then the best rated.
- Browser GatewayAI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.not reviewedGrowingB
Public BrowserChrome over CDP for AI agents. Blind benchmark vs agent-browser: -33% tokens, -33% cost, -32% timenot reviewedGrowingA- nodriver — Chrome browser automationChrome automation via nodriver: 70 tools, isolated browsers, profiles and configurable startup.not reviewedGrowingA
- SeleniumBase MCPStealthy browser automation, testing, and web-scraping via CDP Mode.not reviewedWidely usedA
- SafariNative Safari browser automation for AI agents — 98 tools, zero Chrome overhead.not reviewedEstablishedC