Chrome DevTools MCP Server

Common errors

• Claude Code plugin HTTPS clone failures

  cause 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.

  cause 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`.

Warnings

• gotcha The `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.
• gotcha Performance 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.
• gotcha Usage 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.
• breaking The 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.
• breaking The 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.

Install

• npm install chrome-devtools-mcp npm
• yarn add chrome-devtools-mcp yarn
• pnpm add chrome-devtools-mcp pnpm

Imports

• 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.

Quickstart

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"]
    }
  }
}