CheckOps home

Tools directory

C

CheckOps

Chrome DevTools MCP

Chrome DevTools MCP is Google's Apache-2.0 MCP server and CLI that lets coding agents control and inspect a live Chrome: automation, network and console debugging, and performance traces.

Visit website

Latest public signals

Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.

Visit Website

Introduction

Chrome DevTools for agents (chrome-devtools-mcp) lets a coding agent such as Antigravity, Claude, Cursor or Copilot control and inspect a live Chrome browser. It is available as a Model Context Protocol server and as a CLI. The repository ChromeDevTools/chrome-devtools-mcp is Apache-2.0 licensed.

Its key features are performance insights from recorded DevTools traces, advanced debugging (network requests, screenshots, console messages with source-mapped stack traces) and reliable automation built on Puppeteer that waits for action results.

Features

  1. Performance traces: Record traces and extract actionable performance insights.
  2. Network debugging: Analyse network requests.
  3. Console: Read console messages with source-mapped stack traces.
  4. Screenshots: Capture the page.
  5. Automation: Puppeteer-based actions with automatic waiting.
  6. CLI and skills: A CLI and skills alongside the MCP server.

Pros

  1. Official Chrome team project: Maintained under the ChromeDevTools organisation.
  2. Debugging depth: Goes beyond clicking to network, console and performance.
  3. Free: Apache-2.0.
  4. Very popular: About 55,000 GitHub stars at review.
  5. Works with many agents: Any MCP client.

Cons

  1. Chrome only: No Firefox or Safari.
  2. Exposes browser data: The README warns that MCP clients can inspect and modify any data in the browser; avoid sensitive sessions.
  3. Not a test runner: No assertions or reports.
  4. Agent judgment: Results depend on the agent’s interpretation.
  5. Local browser: Needs Chrome on the machine.

Add the server to an MCP client with npx chrome-devtools-mcp@latest as the command (see the README for client-specific config). Then ask your agent, for example, to load a page, record a performance trace and report the largest contentful paint and failing network requests.

Resources:

Pricing

Chrome DevTools MCP is free and open source under Apache-2.0.

  1. Coding-agent users who want the agent to debug and profile in Chrome.
  2. Web performance engineers automating trace analysis.
  3. Frontend teams checking console and network errors after changes.
  4. Not a fit for cross-browser testing.

Conclusion

Chrome DevTools MCP gives agents real DevTools capabilities: automation, debugging and performance traces in Chrome.

Use a clean browser profile and pair it with a test runner for repeatable checks.

Alternatives

Other tools on CheckOps that cover similar ground. Open a page, or compare one with Chrome DevTools MCP side by side.