Chrome DevTools MCP

Official

The Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants

How to install ↓ Compare GitHub source repository ↗

Category: Browser #2 of 32
Stars: ★ 53.8k Very popular
Transport: stdio (local process)
Runtime: Node.js LTS · Prebuilt binary Chrome stable
Credentials: No credential needed
License: Apache-2.0
Last commit: 3 days ago
Tools: 22

76FMRS · B

Maintained by the official Chrome DevTools team; tools are organized into input automation, navigation, emulation, performance, and network categories with broad coverage and a dedicated troubleshooting doc. A one-line npx command starts it. This review is a static check of source and docs, not an actual run.

Strongest · Setup experience 17/20 Weakest · Security and permissions 12/20

Reliability

13/20

Security and permissions

12/20

Maintenance

17/20

Documentation

17/20

Setup experience

17/20

Test out of dateListed 2026-07-24

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

Best for

Frontend developers who want AI-assisted web debugging and performance analysis
Scenarios that need browser automation and performance diagnostics in the same tool

Not for

Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)

Required permissions

Requires a local Chrome browser instance to run
navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page

Risks and side effects

Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information

Setup

Before you start

Runtime：Node.js LTS · Prebuilt binary Chrome stable

Other optional settings (5)

CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS optional Set to disable Google usage statistics collection (also via --no-usage-statistics flag).

CI optional If set, usage statistics collection is automatically disabled.

CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS optional Set to disable periodic npm update checks.

DEBUG optional Set to * to enable verbose debug logs written to the log file, useful for bug reports.

PROGRAMFILES optional Required in the Codex CLI Windows 11 config, pointing to C:\\Program Files.

Start via npx -y chrome-devtools-mcp@latest — the @latest tag ensures you always run the newest version. For basic browser tasks only, add the --slim flag for a leaner mode with fewer tools enabled.

.mcp.json

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

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the config to your MCP client, confirm tools like click, navigate_page and take_screenshot appear in the client's tool list, then run the prompt 'Check the performance of https://developers.chrome.com' — the client should open Chrome and record a performance trace.

Troubleshooting

Tools don't respond: confirm Chrome has started correctly and the MCP client has permission to connect
Performance trace results look off: make sure no other process was competing for system resources during the trace, skewing the data
Element actions fail: check the common issues listed in docs/troubleshooting.md

Things to try

Once connected, you can ask your AI assistant things like:

Check the performance of https://developers.chrome.com
Open https://example.com and take a screenshot
List all currently open browser pages
Fill the login form and click the submit button

Tools 22

click writes

Click a page element

drag writes

Drag a page element

fill writes

Fill a single input field

fill_form writes

Fill multiple form fields at once

handle_dialog writes

Handle a browser dialog (alert/confirm/prompt)

hover read-only

Hover over a page element

press_key writes

Simulate a key press

type_text writes

Type text

Show 14 more tools

upload_file writes

Upload a file

click_at writes

Click at specific coordinates

close_page writes

Close a page

list_pages read-only

List all currently open pages

navigate_page writes

Navigate a page to a URL

new_page writes

Open a new page

select_page read-only

Switch to a specific page

wait_for read-only

Wait for a condition to be met

emulate writes

Emulate a device/network environment

resize_page writes

Resize the page viewport

performance_analyze_insight read-only

Analyze a specific insight from a performance trace

performance_start_trace writes

Start recording a performance trace

performance_stop_trace read-only

Stop the performance trace and return results

get_network_request read-only

Get details of a specific network request

Use cases

Have an AI assistant analyze a performance trace to pinpoint what's slowing page load

Automate filling forms and clicking through a web task

Inspect a specific network request's response and timing

Emulate different devices and network conditions to test page adaptation

Supported clients

Claude Code

VS Code

Cursor

Windsurf

JetBrains IDEs

Cline

Amp

Kiro

Antigravity

Listed from the project's documentation, not tested by this site.

Overview

Officially maintained by the Google Chrome DevTools team, this MCP server exposes browser input automation, navigation control, device emulation, performance trace analysis, and network request inspection to AI coding assistants — for debugging web issues, analyzing performance bottlenecks, and automating browser actions.

Similar servers

Playwright MCP 78 · B

Microsoft's official Playwright-based browser automation MCP server

★ 38.3k · Tools 10 Compare with this →

FSB MCP Server 66 · C

Control the FSB browser extension from any MCP client for DOM-first AI browser automation.

★ 195 · Tools 30 Compare with this →

Playwright MCP Server 66 · C

Playwright-based browser automation MCP server

★ 5.7k · Tools 1 Compare with this →

DrissionPage MCP Server 64 · C

Local browser automation MCP server powered by DrissionPage

★ 488 · Tools 69 Compare with this →

Compare with other MCP servers

Source revision ff5204aaf572 Data synced 2026-10-19 Read the FMRS scoring method