Registry / llm-agents / chrome-devtools-mcp

chrome-devtools-mcp

library0.21.0jsnpmunverified

The `chrome-devtools-mcp` package provides a Model-Context-Protocol (MCP) server that enables AI coding agents (such as Gemini, Claude, Cursor, or Copilot) to programmatically control and inspect a live Chrome browser instance. It leverages the full capabilities of Chrome DevTools for advanced debugging, performance analysis, and reliable browser automation. Key features include recording traces for performance insights, analyzing network requests, taking screenshots, and monitoring browser console messages with source-mapped stack traces. The server, currently at version 0.21.0, is actively maintained with frequent minor and patch releases. It utilizes Puppeteer for browser automation and officially supports Google Chrome and Chrome for Testing, requiring Node.js v20.19 or newer. This server acts as a bridge, allowing AI agents to interact with the browser context, providing a powerful environment for web development workflows.

llm-agents http-networking testing

npm install chrome-devtools-mcp

github ↗package ↗

INSTALL

IMPORT

SIG · CHROME-DEVTOOLS-MC

chrome-devtools-mcp

llm-agentsjavascriptv0.21.0

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

runCLI

✓ import { runCLI } from 'chrome-devtools-mcp'

Assumed programmatic entry point for invoking the CLI, common for testing or embedding CLI tools.

startServer

✓ import { startServer } from 'chrome-devtools-mcp'

Assumed programmatic entry point to start the MCP server directly within a Node.js application.

McpServerOptions

✓ import type { McpServerOptions } from 'chrome-devtools-mcp'

Assumed type definition for configuration options when starting the server programmatically.

Demonstrates the configuration snippet for an MCP client to integrate and run the `chrome-devtools-mcp` server, including a `--slim` mode example.

{ "mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"] } } } // For basic browser tasks with reduced resource usage and token savings: { "mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest", "--slim", "--headless"] } } }

chrome-devtools-mcp --version

Debug

Known issues

gotchaThe `chrome-devtools-mcp` server exposes the entire browser instance content to connected MCP clients, allowing them to inspect, debug, and modify any data in the browser or DevTools. This includes potentially sensitive or personal information.

fix

Avoid sharing sensitive or personal information in the browser instance when using the MCP server. Ensure that all MCP clients connected to the server are trusted and authorized.

affects: all current versions

gotchaPerformance tools integrated with `chrome-devtools-mcp` may send trace URLs to the Google CrUX API to fetch real-user experience data (Chrome User Experience Report) by default. This data collection helps provide a holistic performance picture but involves external API calls.

fix

To disable the collection and sending of performance data to the Google CrUX API, run the server with the `--no-performance-crux` command-line flag.

affects: all current versions

gotchaUsage statistics, including tool invocation success rates, latency, and environment information, are collected by Google by default to improve the reliability and performance of `chrome-devtools-mcp`.

fix

To opt-out of usage statistics collection, pass the `--no-usage-statistics` flag when starting the server, or set the `CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS` or `CI` environment variables.

affects: all current versions

breakingThe package officially supports only Google Chrome and Chrome for Testing. While other Chromium-based browsers might work, their functionality is not guaranteed and may lead to unexpected behavior.

fix

Ensure you are using Google Chrome (current stable version or newer) or Chrome for Testing for guaranteed compatibility and support.

affects: all current versions

breakingThe package requires Node.js v20.19 or a newer LTS version (e.g., v22.12 or >=23). Older Node.js versions are not supported and will prevent the server from running.

fix

Upgrade your Node.js installation to v20.19, v22.12, or a newer compatible LTS version. Use tools like `nvm` or `fnm` for easy version management.

affects: <=0.21.0 (engines field)

Errors

Common errors & fixes

Claude Code plugin HTTPS clone failures

Specific issue related to the Claude Code plugin's interaction with HTTPS cloning operations.

fix

Refer to the official `chrome-devtools-mcp` troubleshooting documentation for specific guidance on resolving Claude Code plugin HTTPS clone failures.

Error: The 'chrome-devtools-mcp' package requires Node.js v20.19.0 || ^22.12.0 || >=23.

The installed Node.js version does not meet the minimum requirements specified in the package's `engines` field.

fix

Upgrade your Node.js environment to a compatible version (e.g., v20.19.0, v22.12.0, or newer) using a Node.js version manager like `nvm` or `fnm`.

Upgrade

Version history

0.21.0latest on npm

Audit

Dependencies

puppeteerrequiredUsed internally for reliable browser automation.

Agent activity

54 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/ChromeDevTools/chrome-devtools-mcp ↗

packagehttps://www.npmjs.com/package/chrome-devtools-mcp ↗