What problem it solves

Chrome DevTools for agents (`chrome-devtools-mcp`) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. Both give your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.

Key features

• Browser control and inspection — Give coding agents an MCP server for controlling and inspecting a live Chrome browser through Chrome DevTools.

  Source: README

• Performance analysis — Record browser traces and extract actionable performance insights with Chrome DevTools.

  Source: README

• Browser debugging — Analyze network requests, capture screenshots, and inspect browser console messages, including source-mapped stack traces.

  Source: README, docs/tool-reference.md

• Reliable page automation — Automate actions in Chrome and wait automatically for the results of those actions.

  Source: README

• CLI and agent skills — Use the included CLI from a terminal, and install skills that teach agents how to work with Chrome DevTools tools.

  Source: README, skills

Quick start

Copied verbatim from the project's README.

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest"]
    }
  }
}

npm i chrome-devtools-mcp@latest -g
chrome-devtools navigate_page 1 --url "https://developers.chrome.com"
chrome-devtools take_screenshot 1 --filePath screenshot.png
chrome-devtools stop

Who it may suit

This may suit developers building coding-agent workflows that need browser automation, debugging, performance analysis, or terminal-based browser control.

Topics to discuss

• Which Chrome DevTools workflows should be prioritized in agent-facing workflows?

• How should MCP clients safely handle browser data that may contain sensitive or personal information?

• What additional browser-debugging capabilities would be most useful in future releases?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/ChromeDevTools/chrome-devtools-mcp#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.