Chrome DevTools MCP

What it does

The registry declares a stdio npm distribution. Repository documentation describes browser automation, console and network inspection, screenshots and performance traces. This is most useful when a task needs debugging evidence rather than only a generated interface or a checklist of recommended optimizations.

Best for

A developer investigating a reproducible browser issue who can provide a clean page, expected behavior and a measurable observation. Keep the test browser separate from private sessions and record the specific trace or error that supports a finding.

Tradeoffs

The README says browser and DevTools content is exposed to the client. It also documents enabled-by-default usage statistics, optional performance requests to the CrUX API and update checks, with separate controls. Review those settings and the stated Chrome and Node.js requirements before enabling the connection.

A practical first task

Use the publisher's client configuration guide and a disposable browser profile. Reproduce one issue, collect a bounded observation and compare it with a direct manual inspection. Select the privacy settings you need before working with confidential pages.

What to validate

Check the correct browser instance, visibility of console or network evidence, trace reproducibility and the actual telemetry configuration. The metadata review does not establish a performance improvement, browser isolation or runtime safety, and the server was not executed.

Compatibility

cursor, claude-code, gemini-cli

Repository setup documentation; protocol compatibility is not a runtime test

Compatibility source

Installation and requirements

The checked README requires a supported Node.js LTS runtime, npm and Google Chrome or Chrome for Testing. Review telemetry, CrUX requests and update-check controls before using private pages.

Illustrative stdio JSON based on the publisher setup, pinned to the registry-declared version. Client configuration formats differ. This example does not change telemetry settings; inspect the linked source controls before enabling the server.

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

Use your agent’s MCP settings and the publisher’s exact setup. Match the declared transport and package version. Credentials belong in your client’s supported secret storage. No command on this page is run by AI Craft Pad.

npm package

chrome-devtools-mcp · version 1.12.0 · stdio · runtime Unknown

Read publisher setup ↗

Unknown; source software and connected services may have separate terms.