What it does
chrome-devtools-mcp is a Model Context Protocol (MCP) server that lets a coding agent, for example in Antigravity, Claude, Cursor or Copilot, operate and examine a running Chrome browser using Chrome DevTools. There is also a CLI for people who do not want MCP. Per the repository page, its main capabilities are recording performance traces and extracting insights, debugging by analyzing network requests, taking screenshots and reading console messages with source-mapped stack traces, and automating actions through Puppeteer while waiting for results. You add it to an MCP client with an npx command, and the browser starts only when a tool needs it. A slim mode covers basic browser tasks. It needs a current Node.js LTS, a current stable Chrome and npm, and only Google Chrome and Chrome for Testing are officially supported. It exposes the browser's content to the connected client, so avoid sharing sensitive data. Usage statistics are collected by default and can be turned off with a flag, and performance tools may send trace URLs to the CrUX API unless disabled. The project uses the Apache-2.0 license.
Capabilities
- Performance trace recording with actionable insights
- Network request analysis and screenshots
- Console messages with source-mapped stack traces
- Puppeteer-based browser automation that waits for results
- Slim mode and a CLI alternative to MCP
- Apache-2.0 licensed
When to use it
- Having a coding agent check the performance of a page and read its trace
- Letting an agent debug network or console errors in a running web app
- Giving an agent screenshots and browser actions while it tests code
