---
title: "Chrome DevTools MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/chrome-devtools/
description: "Records browser performance traces and inspects live page, console and network behavior from an MCP client."
---

# Chrome DevTools MCP: review, setup & limitations · Undominated.ai

> Records browser performance traces and inspects live page, console and network behavior from an MCP client.

[← Explore all mcp servers](/mcp-servers/)

BROWSER DIAGNOSTICS / Google / Chrome DevTools

# Chrome DevTools MCP

Records browser performance traces and inspects live page, console and network behavior from an MCP client.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp)

SOURCE REVIEW

 Reviewed 2026-10-13
 Evidence 7 linked sources
 Publisher Google / Chrome DevTools
 Licence [Apache-2.0 ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/LICENSE)
 Revision bdc7e243a8d3
 [Read what was—and wasn’t—checked ↓](#review)

“Chrome DevTools for agents”

 [Google / Chrome DevTools · upstream description ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Adds live performance tracing and diagnostic insights alongside browser automation, complementing the separate Playwright and Perfetto selections.
- Console and network tools connect a visible page problem to requests, errors and browser state.

### A good fit for

 - Investigating a slow or broken web page in a controlled Chrome session.
- Collecting a trace and browser evidence while reproducing a frontend bug.

### Weigh up before choosing

 - The connected assistant can inspect and modify browser content. The documented default uses a persistent browser profile; use --isolated when launching Chrome with a temporary profile and avoid unrelated sensitive sessions.
- Usage telemetry is enabled by default, performance tools may query CrUX with trace URLs, and update checks contact npm. Each has a documented opt-out.
- Official browser support covers Google Chrome and Chrome for Testing; support for other Chromium browsers is not guaranteed.
- evaluate_script can run JavaScript given inline or loaded from a file on the server’s filesystem. configuration.md says --no-javascript-evaluation is not a sandbox: page scripts and scripts triggered by clicks or typing still run.
- configuration.md warns that a config file the agent can write can change executablePath, chromeArg and URL allow or block lists. Keep that file and its directory out of the agent’s reach.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md and docs/configuration.md: client setup, privacy controls and browser requirements.
- package.json and src/bin/chrome-devtools-mcp-main.ts: package binary and stdio entrypoint.
- src/index.ts, src/tools/performance.ts and docs/tool-reference.md: tool registration, diagnostics and browser authority.
- LICENSE: Apache-2.0 for repository source.

### Our findings

 - The executable connects through StdioServerTransport; connecting to Chrome through debugging endpoints does not turn the MCP transport into HTTP.
- The browser starts when a tool needs it, rather than merely when the MCP connection opens.
- Telemetry, CrUX requests and npm update checks are distinct outbound behaviors with separate controls.
- docs/tool-reference.md at this commit lists input tools (click, drag, fill, fill_form, handle_dialog, hover, press_key, type_text, upload_file, click_at), navigation tools (new_page, navigate_page, select_page, close_page, list_pages, wait_for), performance_start_trace, performance_stop_trace, performance_analyze_insight, list_network_requests, get_network_request, evaluate_script, lighthouse_audit, take_screenshot and take_snapshot. Heap-snapshot tools need --memoryDebugging=true; extension, third-party and WebMCP tools need their category flags.
- configuration.md says tools that read or write local files are restricted to the OS temp directory when the client does not negotiate MCP roots, unless that restriction is disabled. --blockedUrlPattern and --allowedUrlPattern restrict the browser’s network access.

### Not established by this review

 - Server startup, browser attachment, trace accuracy and privacy opt-outs were not runtime tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/README.md)

DOCUMENTED COMMAND

 npx -y chrome-devtools-mcp@latest Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Configure the documented local process in your MCP client; use that client’s linked setup guide if its JSON schema differs.
- Choose the browser session deliberately. For telemetry opt-out add --no-usage-statistics; for CrUX opt-out add --no-performance-crux.
- Set CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS if you also want to disable the documented npm update checks. The supplied @latest command may retrieve a revision newer than this review.
- Add the documented --isolated option when a temporary browser profile is appropriate for the task.
- The command above is the README configuration’s command and args (npx with -y chrome-devtools-mcp@latest), not a separate installer. It was not run.

### Before you start

 - Node.js satisfying the current package engines, npm, and a supported Chrome installation.
- An MCP client permitted to launch the local process and browser.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

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

### Compatibility

MCP clients that can launch a local stdio process; the example uses the documented mcpServers schema. · Google Chrome or Chrome for Testing with the documented Node.js and npm requirements.

### Implementation

TypeScript

### Transports

stdio

### Local browser control

 - Reads page content, network details, console output and the connected browser’s state.
- Can automate interactions and modify page/browser data; configured tools may write diagnostic artifacts.

### Cost model

Repository source is Apache-2.0 licensed. The MCP client, model service and local computing resources are separate.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Setup, browser support and telemetry ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/README.md) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/README.md Supports: summary, descriptionSourceUrl, upstreamDescription, install, compatibility, configExample, limitations, access
- [Browser configuration options ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/docs/configuration.md) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/docs/configuration.md Supports: install, limitations, access, review, Temp-directory file restriction without roots, URL allow and block patterns, Config file lock-down warning, --no-javascript-evaluation is not a sandbox
- [Diagnostic tool reference ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/docs/tool-reference.md) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/docs/tool-reference.md Supports: summary, whySelected, bestFor, review, access, Tool list and flag-gated categories, evaluate_script sourcePath
- [MCP stdio executable ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/src/bin/chrome-devtools-mcp-main.ts) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/src/bin/chrome-devtools-mcp-main.ts Supports: transports, review
- [Performance tools ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/src/tools/performance.ts) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/src/tools/performance.ts Supports: review, whySelected, bestFor
- [Package manifest ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/package.json) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/package.json Supports: language, install.prerequisites, review
- [Repository licence ↗](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/LICENSE) Checked 2026-10-13 https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/LICENSE Supports: license, access.cost

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
