Chrome DevTools MCP

chrome-devtools-mcp lets your coding agent (such as Gemini, Claude, Cursor or Copilot)

control and inspect a live Chrome browser. It acts as a Model-Context-Protocol

(MCP) server, giving your AI coding assistant access to the full power of

Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.

Tool reference | Changelog | Contributing | Troubleshooting | Design Principles

Key features

Get performance insights: Uses [Chrome

DevTools](https://github.com/ChromeDevTools/devtools-frontend) to record

traces and extract actionable performance insights.

Advanced browser debugging: Analyze network requests, take screenshots and

check browser console messages (with source-mapped stack traces).

Reliable automation. Uses

puppeteer to automate actions in

Chrome and automatically wait for action results.

Disclaimers

chrome-devtools-mcp exposes content of the browser instance to the MCP clients

allowing them to inspect, debug, and modify any data in the browser or DevTools.

Avoid sharing sensitive or personal information that you don't want to share with

MCP clients.

Performance tools may send trace URLs to the Google CrUX API to fetch real-user

experience data. This helps provide a holistic performance picture by

presenting field data alongside lab data. This data is collected by the [Chrome

User Experience Report (CrUX)](https://developer.chrome.com/docs/crux). To disable

this, run with the --no-performance-crux flag.

Usage statistics

Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.

Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:

json

"args": ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]

Google handles this data in accordance with the Google Privacy Policy.

Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.

Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.

Requirements

Node.js v20.19 or a newer latest maintenance LTS version.
Chrome current stable version or newer.
npm.

Getting started

Add the following config to your MCP client:

json

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

[!NOTE]
Using chrome-devtools-mcp@latest ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.

If you are interested in doing only basic browser tasks, use the --slim mode:

json

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

See Slim tool reference.

MCP Client configuration

Amp

Follow https://ampcode.com/manual#mcp and use the config provided above. You can also install the Chrome DevTools MCP server using the CLI:

bash

amp mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Antigravity

To use the Chrome DevTools MCP server follow the instructions from to install a custom MCP server. Add the following config to the MCP servers config:

bash

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222",
        "-y"
      ]
    }
  }
}

This will make the Chrome DevTools MCP server automatically connect to the browser that Antigravity is using. If you are not using port 9222, make sure to adjust accordingly.

Chrome DevTools MCP will not start the browser instance automatically using this approach because the Chrome DevTools MCP server connects to Antigravity's built-in browser. If the browser is not already running, you have to start it first by clicking the Chrome icon at the top right corner.

Claude Code

Install via CLI (MCP only)

Use the Claude Code CLI to add the Chrome DevTools MCP server ():

bash

claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Install as a Plugin (MCP + Skills)

[!NOTE]
If you already had Chrome DevTools MCP installed previously for Claude Code, make sure to remove it first from your installation and configuration files.

To install Chrome DevTools MCP with skills, add the marketplace registry in Claude Code:

/plugin marketplace add ChromeDevTools/chrome-devtools-mcp

Then, install the plugin:

/plugin install chrome-devtools-mcp

Restart Claude Code to have the MCP server and skills load (check with /skills).

Cline

Follow https://docs.cline.bot/mcp/configuring-mcp-servers and use the config provided above.

Codex

Follow the

using the standard config from above. You can also install the Chrome DevTools MCP server using the Codex CLI:

bash

codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

On Windows 11

Configure the Chrome install location and increase the startup timeout by updating .codex/config.toml and adding the following env and startup_timeout_ms parameters:

code

[mcp_servers.chrome-devtools]
command = "cmd"
args = [
    "/c",
    "npx",
    "-y",
    "chrome-devtools-mcp@latest",
]
env = { SystemRoot="C:\\Windows", PROGRAMFILES="C:\\Program Files" }
startup_timeout_ms = 20_000

Copilot CLI

Start Copilot CLI:

code

copilot

Start the dialog to add a new MCP server by running:

code

/mcp add

Configure the following fields and press CTRL+S to save the configuration:

Server name: chrome-devtools
Server Type: [1] Local
Command: npx -y chrome-devtools-mcp@latest

Copilot / VS Code

Click the button to install:

Or install manually:

Follow the MCP install ,

with the standard config from above. You can also install the Chrome DevTools MCP server using the VS Code CLI:

For macOS and Linux:

bash

code --add-mcp '{"name":"io.github.ChromeDevTools/chrome-devtools-mcp","command":"npx","args":["-y","chrome-devtools-mcp"],"env":{}}'

For Windows (PowerShell):

powershell

code --add-mcp '{"""name""":"""io.github.ChromeDevTools/chrome-devtools-mcp""","""command""":"""npx""","""args""":["""-y""","""chrome-devtools-mcp"""]}'

Cursor

Click the button to install:

Or install manually:

Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.

Factory CLI

Use the Factory CLI to add the Chrome DevTools MCP server ():

bash

droid mcp add chrome-devtools "npx -y chrome-devtools-mcp@latest"

Gemini CLI

Install the Chrome DevTools MCP server using the Gemini CLI.

Project wide:

bash

# Either MCP only:
gemini mcp add chrome-devtools npx chrome-devtools-mcp@latest
# Or as a Gemini extension (MCP+Skills):
gemini extensions install --auto-update https://github.com/ChromeDevTools/chrome-devtools-mcp

Globally:

bash

gemini mcp add -s user chrome-devtools npx chrome-devtools-mcp@latest

Alternatively, follow the and use the standard config from above.

Gemini Code Assist

Follow the

using the standard config from above.

JetBrains AI Assistant & Junie

Go to Settings | Tools | AI Assistant | Model Context Protocol (MCP) -> Add. Use the config provided above.

The same way chrome-devtools-mcp can be configured for JetBrains Junie in Settings | Tools | Junie | MCP Settings -> Add. Use the config provided above.

Kiro

In Kiro Settings, go to Configure MCP > Open Workspace or User MCP Config > Use the configuration snippet provided above.

Or, from the IDE Activity Bar > Kiro > MCP Servers > Click Open MCP Config. Use the configuration snippet provided above.

Katalon Studio

The Chrome DevTools MCP server can be used with via an MCP proxy.

Step 1: Install the MCP proxy by following the .

Step 2: Start the Chrome DevTools MCP server with the proxy:

bash

mcp-proxy --transport streamablehttp --port 8080 -- npx -y chrome-devtools-mcp@latest

Note: You may need to pick another port if 8080 is already in use.

Step 3: In Katalon Studio, add the server to StudioAssist with the following settings:

Connection URL: http://127.0.0.1:8080/mcp
Transport type: HTTP

Once connected, the Chrome DevTools MCP tools will be available in StudioAssist.

OpenCode

Add the following configuration to your opencode.json file. If you don't have one, create it at ~/.config/opencode/opencode.json ():

json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrome-devtools": {
      "type": "local",
      "command": ["npx", "-y", "chrome-devtools-mcp@latest"]
    }
  }
}

Qoder

In Qoder Settings, go to MCP Server > + Add > Use the configuration snippet provided above.

Alternatively, follow the and use the standard config from above.

Qoder CLI

Install the Chrome DevTools MCP server using the Qoder CLI ():

Project wide:

bash

qodercli mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Globally:

bash

qodercli mcp add -s user chrome-devtools -- npx chrome-devtools-mcp@latest

Visual Studio

Click the button to install:

Warp

Go to Settings | AI | Manage MCP Servers -> + Add to add an MCP Server. Use the config provided above.

Windsurf

Follow the

using the standard config from above.

Your first prompt

Enter the following prompt in your MCP Client to check if everything is working:

code

Check the performance of https://developers.chrome.com

Your MCP client should open the browser and record a performance trace.

[!NOTE]
The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.

Tools

If you run into any issues, checkout our troubleshooting guide.

Input automation (9 tools)
[click](docs/tool-reference.md#click)
[drag](docs/tool-reference.md#drag)
[fill](docs/tool-reference.md#fill)
[fill_form](docs/tool-reference.md#fill_form)
[handle_dialog](docs/tool-reference.md#handle_dialog)
[hover](docs/tool-reference.md#hover)
[press_key](docs/tool-reference.md#press_key)
[type_text](docs/tool-reference.md#type_text)
[upload_file](docs/tool-reference.md#upload_file)
Navigation automation (6 tools)
[close_page](docs/tool-reference.md#close_page)
[list_pages](docs/tool-reference.md#list_pages)
[navigate_page](docs/tool-reference.md#navigate_page)
[new_page](docs/tool-reference.md#new_page)
[select_page](docs/tool-reference.md#select_page)
[wait_for](docs/tool-reference.md#wait_for)
Emulation (2 tools)
[emulate](docs/tool-reference.md#emulate)
[resize_page](docs/tool-reference.md#resize_page)
Performance (4 tools)
[performance_analyze_insight](docs/tool-reference.md#performance_analyze_insight)
[performance_start_trace](docs/tool-reference.md#performance_start_trace)
[performance_stop_trace](docs/tool-reference.md#performance_stop_trace)
[take_memory_snapshot](docs/tool-reference.md#take_memory_snapshot)
Network (2 tools)
[get_network_request](docs/tool-reference.md#get_network_request)
[list_network_requests](docs/tool-reference.md#list_network_requests)
Debugging (6 tools)
[evaluate_script](docs/tool-reference.md#evaluate_script)
[get_console_message](docs/tool-reference.md#get_console_message)
[lighthouse_audit](docs/tool-reference.md#lighthouse_audit)
[list_console_messages](docs/tool-reference.md#list_console_messages)
[take_screenshot](docs/tool-reference.md#take_screenshot)
[take_snapshot](docs/tool-reference.md#take_snapshot)

Configuration

The Chrome DevTools MCP server supports the following configuration option:

**--autoConnect/ --auto-connect**

If specified, automatically connects to a browser (Chrome 144+) running locally from the user data directory identified by the channel param (default channel is stable). Requires the remoted debugging server to be started in the Chrome instance via chrome://inspect/#remote-debugging.

Type: boolean
Default: false

**--browserUrl/ --browser-url, -u**

Connect to a running, debuggable Chrome instance (e.g. http://127.0.0.1:9222). For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp#connecting-to-a-running-chrome-instance.

Type: string

**--wsEndpoint/ --ws-endpoint, -w**

WebSocket endpoint to connect to a running Chrome instance (e.g., ws://127.0.0.1:9222/devtools/browser/). Alternative to --browserUrl.

Type: string

**--wsHeaders/ --ws-headers**

Custom headers for WebSocket connection in JSON format (e.g., '{"Authorization":"Bearer token"}'). Only works with --wsEndpoint.

Type: string

**--headless**

Whether to run in headless (no UI) mode.

Type: boolean
Default: false

**--executablePath/ --executable-path, -e**

Path to custom Chrome executable.

Type: string

**--isolated**

If specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed. Defaults to false.

Type: boolean

**--userDataDir/ --user-data-dir**

Path to the user data directory for Chrome. Default is $HOME/.cache/chrome-devtools-mcp/chrome-profile$CHANNEL_SUFFIX_IF_NON_STABLE

Type: string

**--channel**

Specify a different Chrome channel that should be used. The default is the stable channel version.

Type: string
Choices: stable, canary, beta, dev

**--logFile/ --log-file**

Path to a file to write debug logs to. Set the env variable DEBUG to * to enable verbose logs. Useful for submitting bug reports.

Type: string

**--viewport**

Initial viewport size for the Chrome instances started by the server. For example, 1280x720. In headless mode, max size is 3840x2160px.

Type: string

**--proxyServer/ --proxy-server**

Proxy server configuration for Chrome passed as --proxy-server when launching the browser. See https://www.chromium.org/developers/design-documents/network-settings/ for details.

Type: string

**--acceptInsecureCerts/ --accept-insecure-certs**

If enabled, ignores errors relative to self-signed and expired certificates. Use with caution.

Type: boolean

**--experimentalScreencast/ --experimental-screencast**

Exposes experimental screencast tools (requires ffmpeg). Install ffmpeg https://www.ffmpeg.org/download.html and ensure it is available in the MCP server PATH.

Type: boolean

**--chromeArg/ --chrome-arg**

Additional arguments for Chrome. Only applies when Chrome is launched by chrome-devtools-mcp.

Type: array

**--ignoreDefaultChromeArg/ --ignore-default-chrome-arg**

Explicitly disable default arguments for Chrome. Only applies when Chrome is launched by chrome-devtools-mcp.

Type: array

**--categoryEmulation/ --category-emulation**

Set to false to exclude tools related to emulation.

Type: boolean
Default: true

**--categoryPerformance/ --category-performance**

Set to false to exclude tools related to performance.

Type: boolean
Default: true

**--categoryNetwork/ --category-network**

Set to false to exclude tools related to network.

Type: boolean
Default: true

**--performanceCrux/ --performance-crux**

Set to false to disable sending URLs from performance traces to CrUX API to get field performance data.

Type: boolean
Default: true

**--usageStatistics/ --usage-statistics**

Set to false to opt-out of usage statistics collection. Google collects usage data to improve the tool, handled under the Google Privacy Policy (https://policies.google.com/privacy). This is independent from Chrome browser metrics. Disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.

Type: boolean
Default: true

**--slim**

Exposes a "slim" set of 3 tools covering navigation, script execution and screenshots only. Useful for basic browser tasks.

Type: boolean

Pass them via the args property in the JSON configuration. For example:

json

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--channel=canary",
        "--headless=true",
        "--isolated=true"
      ]
    }
  }
}

Connecting via WebSocket with custom headers

You can connect directly to a Chrome WebSocket endpoint and include custom headers (e.g., for authentication):

json

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--wsEndpoint=ws://127.0.0.1:9222/devtools/browser/",
        "--wsHeaders={\"Authorization\":\"Bearer YOUR_TOKEN\"}"
      ]
    }
  }
}

To get the WebSocket endpoint from a running Chrome instance, visit http://127.0.0.1:9222/json/version and look for the webSocketDebuggerUrl field.

You can also run npx chrome-devtools-mcp@latest --help to see all available configuration options.

Concepts

User data directory

chrome-devtools-mcp starts a Chrome's stable channel instance using the following user

data directory:

Linux / macOS: $HOME/.cache/chrome-devtools-mcp/chrome-profile-$CHANNEL
Windows: %HOMEPATH%/.cache/chrome-devtools-mcp/chrome-profile-$CHANNEL

The user data directory is not cleared between runs and shared across

all instances of chrome-devtools-mcp. Set the isolated option to true

to use a temporary user data dir instead which will be cleared automatically after

the browser is closed.

Connecting to a running Chrome instance

By default, the Chrome DevTools MCP server will start a new Chrome instance with a dedicated profile. This might not be ideal in all situations:

If you would like to maintain the same application state when alternating between manual site testing and agent-driven testing.
When the MCP needs to sign into a website. Some accounts may prevent sign-in when the browser is controlled via WebDriver (the default launch mechanism for the Chrome DevTools MCP server).
If you're running your LLM inside a sandboxed environment, but you would like to connect to a Chrome instance that runs outside the sandbox.

In these cases, start Chrome first and let the Chrome DevTools MCP server connect to it. There are two ways to do so:

Automatic connection (available in Chrome 144): best for sharing state between manual and agent-driven testing.
Manual connection via remote debugging port: best when running inside a sandboxed environment.

Automatically connecting to a running Chrome instance

Step 1: Set up remote debugging in Chrome

In Chrome (\>= M144), do the following to set up remote debugging:

1. Navigate to chrome://inspect/#remote-debugging to enable remote debugging.

2. Follow the dialog UI to allow or disallow incoming debugging connections.

Step 2: Configure Chrome DevTools MCP server to automatically connect to a running Chrome Instance

To connect the chrome-devtools-mcp server to the running Chrome instance, use

--autoConnect command line argument for the MCP server.

The following code snippet is an example configuration for gemini-cli:

json

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

Step 3: Test your setup

Make sure your browser is running. Open gemini-cli and run the following prompt:

none

Check the performance of https://developers.chrome.com

[!NOTE]
The autoConnect option requires the user to start Chrome. If the user has multiple active profiles, the MCP server will connect to the default profile (as determined by Chrome). The MCP server has access to all open windows for the selected profile.

The Chrome DevTools MCP server will try to connect to your running Chrome

instance. It shows a dialog asking for user permission.

Clicking Allow results in the Chrome DevTools MCP server opening

developers.chrome.com and taking a performance

trace.

Manual connection using port forwarding

You can connect to a running Chrome instance by using the --browser-url option. This is useful if you are running the MCP server in a sandboxed environment that does not allow starting a new Chrome instance.

Here is a step-by-step guide on how to connect to a running Chrome instance:

Step 1: Configure the MCP client

Add the --browser-url option to your MCP client configuration. The value of this option should be the URL of the running Chrome instance. http://127.0.0.1:9222 is a common default.

json

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222"
      ]
    }
  }
}

Step 2: Start the Chrome browser

[!WARNING]
Enabling the remote debugging port opens up a debugging port on the running browser instance. Any application on your machine can connect to this port and control the browser. Make sure that you are not browsing any sensitive websites while the debugging port is open.

Start the Chrome browser with the remote debugging port enabled. Make sure to close any running Chrome instances before starting a new one with the debugging port enabled. The port number you choose must be the same as the one you specified in the --browser-url option in your MCP client configuration.

For security reasons, Chrome requires you to use a non-default user data directory when enabling the remote debugging port. You can specify a custom directory using the --user-data-dir flag. This ensures that your regular browsing profile and data are not exposed to the debugging session.

macOS

bash

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-profile-stable

Linux

bash

/usr/bin/google-chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-profile-stable

Windows

bash

"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="%TEMP%\chrome-profile-stable"

Step 3: Test your setup

After configuring the MCP client and starting the Chrome browser, you can test your setup by running a simple prompt in your MCP client:

code

Check the performance of https://developers.chrome.com

Your MCP client should connect to the running Chrome instance and receive a performance report.

If you hit VM-to-host port forwarding issues, see the “Remote debugging between virtual machine (VM) and host fails” section in [docs/troubleshooting.md](./docs/troubleshooting.md#remote-debugging-between-virtual-machine-vm-and-host-fails).

For more details on remote debugging, see the Chrome DevTools documentation.

Debugging Chrome on Android

Please consult these instructions.

Known limitations

See Troubleshooting.

Chrome Devtools Mcp

Documentation

Chrome DevTools MCP

Tool reference | Changelog | Contributing | Troubleshooting | Design Principles

Key features

Disclaimers

Usage statistics

Requirements

Getting started

MCP Client configuration

Your first prompt

Tools

Configuration

Connecting via WebSocket with custom headers

Concepts

User data directory

Connecting to a running Chrome instance

Automatically connecting to a running Chrome instance

Manual connection using port forwarding

Debugging Chrome on Android

Known limitations

Similar MCP

Mcp Server Browserbase

Mcp Open Library

Mcp Ipfs

Liveblocks Mcp Server

Trending MCP

Playwright Mcp

Serena

Mcp Playwright

Mcp Server Cloudflare

Mcp Server Browserbase

Mcp Open Library

Mcp Ipfs

Liveblocks Mcp Server

Playwright Mcp

Serena

Mcp Playwright

Mcp Server Cloudflare