Chrome DevTools MCP
Official Google ChromeDevTools MCP server giving Claude programmatic access to Chrome DevTools: performance profiling, network inspection, DOM manipulation, and Lighthouse audits. 2.55M monthly npm downloads.
- Find out why your website loads slowly and get fix suggestions
- Run a quality audit on any web page and get a score report
- Identify broken links or missing images on your site
Frontend debugging and performance analysis are time-intensive. AI assistants with direct DevTools access can assist with performance optimization, accessibility auditing, and bug diagnosis — a high-value workflow for frontend teams.
Frontend developers and web performance engineers who want AI-assisted analysis of browser performance, network requests, and page quality metrics.
https://www.npmjs.com/package/chrome-devtools-mcp
By Google LLC
How to Get It
npx -y chrome-devtools-mcp
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Trust Signals Source Reviewed
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- Chrome DevTools MCP (2025) — Hacker News · 604 pts
- I've successfully converted 'chrome-devtools-mcp' into Agent Skills — Reddit · 179 pts
- Chrome DevTools MCP + Obsidian = Unlimited power — Reddit · 94 pts
19 mentions across 2 sources
Reviewer notes
Source Reviewed review. These are observations, not a security certification.
Official Google ChromeDevTools org package. 2.55M monthly downloads, Apache 2.0 license. Zero runtime npm dependencies (all bundled) — excellent for security. Maintained by Google engineers. Pre-1.0 (API instability). Requires Chrome running with remote debugging port open.
Remote debugging access to Chrome: can read page content, network traffic, cookies, and DOM — full browser session visibility. Appropriate for local development but dangerous in shared/cloud environments. Zero runtime dependencies is strong supply chain posture. Requires explicit Chrome debugging port configuration.
2026-04-02: LIMITATION: Requires Chrome running with remote debugging port open — that port grants full browser session visibility (cookies, network, DOM). Dangerous in shared or cloud environments.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Official Google ChromeDevTools org package. 2.55M monthly downloads, Apache 2.0 license. Zero runtime npm dependencies (all bundled) — excellent for security. Maintained by Google engineers. Pre-1.0 (API instability). Requires Chrome running with remote debugging port open.