Undominated.ai
← Explore all 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 ↓Original source ↗

“Chrome DevTools for agents”

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.

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 ↗

DOCUMENTED COMMAND

npx -y chrome-devtools-mcp@latest

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

  1. Configure the documented local process in your MCP client; use that client’s linked setup guide if its JSON schema differs.
  2. Choose the browser session deliberately. For telemetry opt-out add --no-usage-statistics; for CrUX opt-out add --no-performance-crux.
  3. 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.
  4. Add the documented --isolated option when a temporary browser profile is appropriate for the task.
  5. 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"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. Setup, browser support and telemetry ↗Checked

    https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/README.md

    Supports: summary, descriptionSourceUrl, upstreamDescription, install, compatibility, configExample, limitations, access

  2. Browser configuration options ↗Checked

    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

  3. Diagnostic tool reference ↗Checked

    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

  4. MCP stdio executable ↗Checked

    https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/src/bin/chrome-devtools-mcp-main.ts

    Supports: transports, review

  5. Performance tools ↗Checked

    https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/src/tools/performance.ts

    Supports: review, whySelected, bestFor

  6. Package manifest ↗Checked

    https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/package.json

    Supports: language, install.prerequisites, review

  7. Repository licence ↗Checked

    https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/bdc7e243a8d3397e871607fdb5c56cc7115ec5ae/LICENSE

    Supports: license, access.cost

Evidence & Ask
Markdown for LLMs