home / mcp / chrome devtools mcp server

Chrome DevTools MCP Server

Provides a live Chrome DevTools MCP server to automate, debug, and analyze Chrome with your MCP clients.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "chromedevtools-chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest"
      ]
    }
  }
}

You can connect an AI coding assistant to a live Chrome browser via the Chrome DevTools MCP server. It exposes Chrome DevTools capabilities through the MCP protocol, enabling automated control, in-depth debugging, performance analysis, and reliable browser automation for your prompts and workflows.

How to use

Use the Chrome DevTools MCP server to let your MCP client perform actions in Chrome, inspect network activity, capture screenshots, and analyze performance traces. Start your MCP client with the chrome-devtools server configured, and issue prompts that request browser interactions or devtools insights. The server will launch or connect to a Chrome instance as needed and expose tool capabilities such as navigation, input automation, network inspection, emulation, performance analysis, and debugging.

How to install

Prerequisites: you need Node.js (v20.19 or newer LTS), Chrome current stable version or newer, and npm installed on your system.

Install and run the MCP server using the standard configuration shown here. You can copy this exact snippet into your MCP client configuration to enable the Chrome DevTools MCP server.

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest"]
    }
  }
}

Configuration and usage notes

The server supports connecting to a running Chrome instance or launching its own. You can adjust behavior with command line options such as connecting to a browser URL, enabling or disabling usage statistics, and choosing a Chrome channel. If you want to connect to a running Chrome instance, provide the browser URL (for example, http://127.0.0.1:9222) in the MCP client configuration.

Your first prompt

To verify everything is working, run a prompt that asks to check the performance of a web page. The MCP client should launch Chrome (or connect to an existing instance) and record a performance trace.

Example task to try: check the performance of https://developers.chrome.com.

Available tools

input automation

Automates user-like interactions such as clicking, dragging, filling fields, submitting forms, handling dialogs, hovering, pressing keys, and uploading files.

navigation automation

Navigates pages, waits for results, lists or targets pages, and manages multiple pages or tabs.

emulation

Emulates device characteristics and resizes pages to simulate different viewports.

performance

Starts and stops performance traces, analyzes traces, and derives actionable performance insights.

network

Inspects network requests and can fetch specific requests or enumerate network activity.

debugging

Evaluates scripts, accesses console messages, lists console outputs, and captures screenshots or page snapshots.