{"id":14486,"library":"chrome-devtools-mcp","title":"Chrome DevTools MCP Server","description":"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.","status":"active","version":"0.21.0","language":"javascript","source_language":"en","source_url":"https://github.com/ChromeDevTools/chrome-devtools-mcp","tags":["javascript"],"install":[{"cmd":"npm install chrome-devtools-mcp","lang":"bash","label":"npm"},{"cmd":"yarn add chrome-devtools-mcp","lang":"bash","label":"yarn"},{"cmd":"pnpm add chrome-devtools-mcp","lang":"bash","label":"pnpm"}],"dependencies":[{"reason":"Used internally for reliable browser automation.","package":"puppeteer","optional":false}],"imports":[{"note":"Assumed programmatic entry point for invoking the CLI, common for testing or embedding CLI tools.","symbol":"runCLI","correct":"import { runCLI } from 'chrome-devtools-mcp'"},{"note":"Assumed programmatic entry point to start the MCP server directly within a Node.js application.","symbol":"startServer","correct":"import { startServer } from 'chrome-devtools-mcp'"},{"note":"Assumed type definition for configuration options when starting the server programmatically.","symbol":"McpServerOptions","correct":"import type { McpServerOptions } from 'chrome-devtools-mcp'"}],"quickstart":{"code":"{\n  \"mcpServers\": {\n    \"chrome-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"chrome-devtools-mcp@latest\"]\n    }\n  }\n}\n\n// For basic browser tasks with reduced resource usage and token savings:\n{\n  \"mcpServers\": {\n    \"chrome-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"chrome-devtools-mcp@latest\", \"--slim\", \"--headless\"]\n    }\n  }\n}","lang":"json","description":"Demonstrates the configuration snippet for an MCP client to integrate and run the `chrome-devtools-mcp` server, including a `--slim` mode example."},"warnings":[{"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.","message":"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.","severity":"gotcha","affected_versions":"all current versions"},{"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.","message":"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.","severity":"gotcha","affected_versions":"all current versions"},{"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.","message":"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`.","severity":"gotcha","affected_versions":"all current versions"},{"fix":"Ensure you are using Google Chrome (current stable version or newer) or Chrome for Testing for guaranteed compatibility and support.","message":"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.","severity":"breaking","affected_versions":"all current versions"},{"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.","message":"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.","severity":"breaking","affected_versions":"<=0.21.0 (engines field)"}],"env_vars":null,"last_verified":"2026-04-19T00:00:00.000Z","next_check":"2026-07-18T00:00:00.000Z","problems":[{"fix":"Refer to the official `chrome-devtools-mcp` troubleshooting documentation for specific guidance on resolving Claude Code plugin HTTPS clone failures.","cause":"Specific issue related to the Claude Code plugin's interaction with HTTPS cloning operations.","error":"Claude Code plugin HTTPS clone failures"},{"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`.","cause":"The installed Node.js version does not meet the minimum requirements specified in the package's `engines` field.","error":"Error: The 'chrome-devtools-mcp' package requires Node.js v20.19.0 || ^22.12.0 || >=23."}],"ecosystem":"npm"}