Neura Market
ChromeDevTools/chrome-devtools-mcp logo

ChromeDevTools/chrome-devtools-mcp

Free

谷歌 Chrome 官方出品，让 AI 编程代理直接驱动 Chrome DevTools：导航页面、检查 DOM、抓取网络请求、跑性能与 Lighthouse 审计、执行脚本。

FreeFree tier
Type
Open Source
Company
Google
Visit Website GitHub (40 stars)

About ChromeDevTools/chrome-devtools-mcp

Chrome DevTools MCP (Model-Context-Protocol) is an official Google open-source tool that acts as an MCP server, allowing AI coding agents such as Antigravity, Claude, Cursor, and Copilot to directly control and inspect a live Chrome browser. It provides access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. Key capabilities include recording performance traces to extract actionable insights, analyzing network requests, taking screenshots, checking browser console messages with source-mapped stack traces, and automating browser actions with automatic wait for results. A CLI is also provided for non-MCP usage. The tool officially supports Google Chrome and Chrome for Testing, and collects usage statistics by default (configurable).

Key Features

Get performance insights by recording traces and extracting actionable performance data
Advanced browser debugging: analyze network requests, take screenshots, and check console messages with source-mapped stack traces
Reliable automation using Puppeteer with automatic wait for action results
Acts as an MCP server for integration with multiple coding agents (Claude, Cursor, Copilot, etc.)
CLI tool provided for use without MCP
Supports performance analysis with Chrome User Experience Report (CrUX) data (configurable)

Pros & Cons

Pros
  • Official tool from the Chrome DevTools team at Google
  • Open source with an active community and public repository
  • Integrates seamlessly with popular AI coding agents via MCP
  • Provides deep access to Chrome DevTools capabilities including performance traces, network, and console
  • Supports both MCP server and standalone CLI usage
  • Performance analysis includes real-user field data from CrUX
Cons
  • Only officially supports Google Chrome and Chrome for Testing; other Chromium browsers may have unexpected behavior
  • Collects usage statistics by default (can be opted out with --no-usage-statistics flag)
  • Performance tools may send trace URLs to Google CrUX API (can be disabled with --no-performance-crux flag)
  • Exposes the full content of the browser instance to MCP clients, which may be a privacy concern
  • Requires a Chrome browser installation to operate

Best For

Debugging and inspecting web applications during developmentPerformance analysis and optimization of web pagesAutomated browser testing and end-to-end testingAI-driven web scraping and DOM inspectionNetwork request analysis and console log monitoring

FAQ

Which browsers are officially supported?
Chrome DevTools MCP officially supports Google Chrome and Chrome for Testing. Other Chromium-based browsers may work but are not guaranteed and may cause unexpected behavior.
How can I disable usage statistics collection?
Usage statistics are collected by default but can be disabled by passing the --no-usage-statistics flag when starting the server, e.g., 'args: ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]'.
Can I use this tool without an MCP client?
Yes, a CLI is provided for use without MCP. The repository includes a CLI for direct command-line usage.
What data is sent to Google for performance analysis?
Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. This can be disabled with the --no-performance-crux flag.
Does the tool collect Chrome browser usage statistics?
The collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's own usage statistics.