mcp-chrome-cdp

MCP server that gives AI agents full control over Chrome through the Chrome DevTools Protocol. Direct WebSocket connection to Chrome — no Puppeteer, no Playwright, no overhead.

54 tools across 12 categories: navigation, screenshots, JavaScript execution, DOM queries, input simulation, network monitoring, console capture, cookie/storage management, device emulation, performance metrics, accessibility, and browser control.

# macOS
open -a "Google Chrome" --args --remote-debugging-port=9222

# Linux
google-chrome --remote-debugging-port=9222

# Windows
start chrome --remote-debugging-port=9222

git clone https://github.com/YosephFr/mcp-chrome-cdp.git
cd mcp-chrome-cdp
npm install

Create or edit ~/.mcp.json:

{
  "mcpServers": {
    "chrome-cdp": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-chrome-cdp/index.js"]
    }
  }
}

Restart Claude Code. Verify with /mcp — you should see chrome-cdp connected.

The server connects to 127.0.0.1:9222 by default. Override with environment variables:

{
  "mcpServers": {
    "chrome-cdp": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-chrome-cdp/index.js"],
      "env": {
        "CDP_HOST": "127.0.0.1",
        "CDP_PORT": "9222"
      }
    }
  }
}

| Tool | Description | |------|-------------| | chrome_list_tabs | List all open tabs and targets | | chrome_new_tab | Open a new tab with optional URL | | chrome_close_tab | Close a tab by ID | | chrome_activate_tab | Bring a tab to the foreground |

| Tool | Description | |------|-------------| | chrome_navigate | Navigate to a URL (waits for page load) | | chrome_reload | Reload the page, optionally bypassing cache | | chrome_go_back | Naviga