GitHubGitHub RepoNeeds Review

ChromeDevTools/chrome-devtools-mcp

Google's MCP server gives agents a live Chrome: 62+ tools for input, network inspection, performance traces, and console debugging. One npx line wires it into Claude Code or Cursor.

GitHub

Open Source Open Markdown Open JSON

Source Summary

**The gist** The Chrome team's MCP server lets a coding agent drive and inspect a live Chrome instance: **62+ tools** across **nine categories**, including input automation, network inspection, **performance traces**, console and script debugging, and heap snapshots. Setup is one MCP entry pointing at **npx chrome-devtools-mcp@latest**; a slim mode covers basic browsing tasks.

Practical Implication

**Why it matters** This closes the loop for frontend agent work: instead of guessing from code, your agent can reproduce a bug, read the **console and network requests**, record a **performance trace**, and verify the fix in the actual browser — the feedback layer most agent setups are missing.

Agent-Ready Context

**The gist** The Chrome team's MCP server lets a coding agent drive and inspect a live Chrome instance: **62+ tools** across **nine categories**, including input automation, network inspection, **performance traces**, console and script debugging, and heap snapshots. Setup is one MCP entry pointing at **npx chrome-devtools-mcp@latest**; a slim mode covers basic browsing tasks.

**Why it matters** This closes the loop for frontend agent work: instead of guessing from code, your agent can reproduce a bug, read the **console and network requests**, record a **performance trace**, and verify the fix in the actual browser — the feedback layer most agent setups are missing.

**Watch out** Everything in the browser is exposed to the MCP client, so avoid running it against **logged-in sessions with sensitive data**. **Usage statistics are on by default** (opt out with **--no-usage-statistics**), performance tools call Google's CrUX API unless disabled, and only official **Chrome** builds are supported.

Uncertainty

Everything in the browser is exposed to the MCP client, so avoid running it against **logged-in sessions with sensitive data**. **Usage statistics are on by default** (opt out with **--no-usage-statistics**), performance tools call Google's CrUX API unless disabled, and only official **Chrome** builds are supported.