# Chrome DevTools MCP

> Chrome DevTools MCP is an open-source MCP server for browser automation. MCP server giving coding agents control and inspection of a live Chrome browser. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, macOS, Windows, Linux
- **Repository:** https://github.com/dinesh-nalla-se/chrome-devtools-mcp
- **MCP Registry name:** io.github.dinesh-nalla-se/chrome-devtools-mcp
- **Categories:** [browser automation](https://ai-powered.com/categories/browser-automation)
- **Listing updated:** 2026-11-18

## About

The README describes this as a bridge between coding assistants such as Claude, Cursor or Copilot and a running Chrome browser. Once connected, the assistant can drive pages and read back what the browser is doing, using the Chrome DevTools protocol together with Puppeteer for actions that wait for results to settle.

The tool set covers three broad areas: input automation (clicks, forms, drag, key presses, file uploads), navigation and page management, and debugging. Debugging tools expose network requests, console messages, screenshots, DOM snapshots and script evaluation. A separate group records performance traces and returns analysed insights.

The README is explicit that the server exposes page content and browser data to the connected client, so it recommends keeping sensitive sessions out of reach. It is aimed at developers who want an assistant to reproduce bugs, debug front-end issues or measure page performance. Options control headless mode, channel, isolated profiles, proxy settings and which tool categories load.

## Features

- **Performance trace analysis:** Records Chrome performance traces and extracts insights the assistant can act on.
- **Network and console inspection:** Lists and inspects network requests and browser console messages for debugging.
- **Browser automation via Puppeteer:** Performs clicks, typing, form fills and navigation, waiting for results before continuing.
- **Screenshots and DOM snapshots:** Captures page screenshots and accessibility-style snapshots of the current page.
- **Connect to existing Chrome:** Can attach to a running Chrome instance over a remote debugging port or WebSocket endpoint.
- **Configurable tool categories:** Flags let users turn off emulation, performance or network tool groups and choose headless mode.

## Good for

- Asking a coding assistant to record and explain a page's performance trace
- Reproducing a front-end bug by driving the page and reading console errors
- Inspecting failed or slow network requests while developing a web app
- Capturing screenshots of a page state for review inside an AI coding session
- Automating repetitive form or navigation steps in a logged-in Chrome session

## Install

### Claude Code (Terminal)

```sh
claude mcp add chrome-devtools-mcp -- npx -y @dinesh-nalla-se/chrome-devtools-mcp
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dinesh-nalla-se/chrome-devtools-mcp"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dinesh-nalla-se/chrome-devtools-mcp"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "chrome-devtools-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dinesh-nalla-se/chrome-devtools-mcp"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dinesh-nalla-se/chrome-devtools-mcp"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dinesh-nalla-se/chrome-devtools-mcp"
      ]
    }
  }
}
```

## Tools

- `click`: Click an element on the page.
- `drag`: Drag one element onto another.
- `fill`: Fill a single input field.
- `fill_form`: Fill multiple form fields.
- `handle_dialog`: Respond to a browser dialog.
- `hover`: Hover over an element.
- `press_key`: Press a keyboard key.
- `upload_file`: Upload a file to a file input.
- `close_page`: Close a browser page.
- `list_pages`: List open pages.
- `navigate_page`: Navigate a page to a URL.
- `new_page`: Open a new page.
- `select_page`: Select an open page.
- `wait_for`: Wait for text to appear on the page.
- `emulate`: Emulate device or environment settings.
- `resize_page`: Resize the page viewport.
- `performance_analyze_insight`: Analyse a performance insight.
- `performance_start_trace`: Start recording a performance trace.
- `performance_stop_trace`: Stop recording a performance trace.
- `get_network_request`: Get details of a network request.
- `list_network_requests`: List network requests.
- `evaluate_script`: Evaluate a script in the page.
- `get_console_message`: Get a console message.
- `list_console_messages`: List console messages.
- `take_screenshot`: Take a screenshot.
- `take_snapshot`: Take a page snapshot.

## FAQ

### What does it need to run?

The README lists Node.js v20.19 or a newer maintenance LTS version, a current stable Chrome, and npm.

### How is it started?

MCP clients launch it with npx and the chrome-devtools-mcp@latest package; the README gives config snippets for many clients.

### Does it start Chrome by itself?

It starts the browser when a client calls a tool that needs one. Connecting to the server alone does not launch Chrome.

### Can it connect to a browser I already have open?

Yes, using --browser-url or --wsEndpoint with Chrome started with a remote debugging port.

### Is there a security warning?

Yes. The README warns that the server exposes browser content to MCP clients and that an open debugging port lets other local applications control the browser.

### Is Chrome DevTools MCP free?

Yes. Chrome DevTools MCP is open source, so you can use and self-host it for free.

### How do I add Chrome DevTools MCP to Claude Code?

Run this command in your terminal: claude mcp add chrome-devtools-mcp -- npx -y @dinesh-nalla-se/chrome-devtools-mcp

### What are the best alternatives to Chrome DevTools MCP?

The closest alternatives to Chrome DevTools MCP are Chrome DevTools MCP, Brave DevTools MCP, Selenium MCP, Selenium Webdriver MCP and MCP Browser Extension.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [Chrome DevTools MCP](https://ai-powered.com/mcp/chrome-devtools-mcp-4): Chrome DevTools MCP is an open-source MCP server for browser automation.
- [Brave DevTools MCP](https://ai-powered.com/mcp/brave-devtools-mcp): Brave DevTools MCP is an open-source MCP server for browser automation.
- [Selenium MCP](https://ai-powered.com/mcp/selenium-mcp-2): Selenium MCP is an open-source MCP server for browser automation.
- [Selenium Webdriver MCP](https://ai-powered.com/mcp/selenium-webdriver-mcp): Selenium Webdriver MCP is an open-source MCP server for browser automation.
- [MCP Browser Extension](https://ai-powered.com/mcp/mcp-browser-extension): MCP Browser Extension is an open-source MCP server for browser automation.
- [MCP Server Browser](https://ai-powered.com/mcp/mcp-server-browser): MCP Server Browser is an open-source MCP server for browser automation.
- [Agent Browser](https://ai-powered.com/mcp/agent-browser-3): Agent Browser is an open-source MCP server for browser automation.
- [Browser Gateway](https://ai-powered.com/mcp/browser-gateway): Browser Gateway is an MCP server for browser automation.

---
Source: https://ai-powered.com/mcp/chrome-devtools-mcp-3
