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.

Related MCP server: OpenChrome

Install

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

Or 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

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