Local Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Browser MCP Cdp.
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
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.
Different tradeoffs from the alternatives:
| browser-mcp-cdp | Playwright MCP | Chrome DevTools MCP | |
|---|---|---|---|
| Browser | Your local Chrome | Managed Playwright Chromium | Your local Chrome |
| Login state | β Snapshot of your profile (cookies, logins, IndexedDB) | β Fresh profile | β Real profile (modifies it) |
| Profile isolation | β Copy-on-start, real profile untouched | N/A | β οΈ Direct attach |
| Multi-client | β Shared broker across MCP clients | β Per-client | β Per-client |
| Dependencies | Node only (no Playwright download) | Playwright + browsers | Node 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.
Or add manually to ~/.claude.json / Claude Desktop config:
Requires Node 18+ and Google Chrome installed.
| Tool | Purpose |
|---|---|
browser_navigate | Load a URL, return final URL + title |
browser_evaluate | Run JS in the page, return result |
browser_screenshot | PNG of current page |
browser_click | Click via CSS selector |
browser_click_at | Click at pixel coordinates (pierces iframes / overlays) |
browser_fill | Set value on input/textarea/select |
browser_wait_for | Wait for a selector to appear |
browser_get_url | Current URL |
browser_get_text | Visible text of page or element |
browser_get_html | outerHTML of page or element |
browser_scroll | Scroll by (x, y) pixels |
browser_tabs | List open tabs |
browser_new_tab | Open a new tab |
| Var | Default |
|---|---|
BROWSER_MCP_CHROME_PATH | Auto-detected per OS |
BROWSER_MCP_CHROME_PROFILE_ROOT | OS-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_MS | 600000 (10 min) |
--user-data-dir=<temp> and --remote-debugging-port.BROKER_IDLE_TIMEOUT_MS of no activity; temp profile is deleted.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.
MIT
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/browser-mcp-cdp)<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>