# Chrome DevTools MCP

> Chrome DevTools MCP (v1.11.0, Oct 2026, ~54k stars) gives Claude, Cursor, Copilot and other agents control of a real Chrome through Puppeteer, plus DevTools: network requests, console logs, screenshots and performance traces. It can launch Chrome or attach to a running one over a debugging port. Officially supports Chrome only. Google collects usage statistics by default (--no-usage-statistics turns it off), and performance tools may send URLs to the CrUX API. Needs Node.js LTS and current Chrome. Apache-2.0.

- Repository: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Official docs: https://github.com/ChromeDevTools/chrome-devtools-mcp#readme
- Checked: 2026-10-22

## What it replaces
Nothing people pay for: a free tool, listed because people search for it.

## Facts, with sources

| Question | Status | Answer | Source | Checked |
|---|---|---|---|---|
| Runs on my machine? | Confirmed | Yes; runs on your machine with npx and controls a local Chrome | https://github.com/ChromeDevTools/chrome-devtools-mcp#readme | 2026-10-22 |
| Code licence | Confirmed | Apache-2.0 | https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/LICENSE | 2026-10-22 |
| Model weights licence | Confirmed | No separate model weights; works with whatever model your MCP client uses | https://github.com/ChromeDevTools/chrome-devtools-mcp#readme | 2026-10-22 |
| Commercial use | Confirmed | Yes, Apache-2.0 | https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/LICENSE | 2026-10-22 |
| Paid services needed? | Confirmed | None required; usage statistics go to Google unless you pass --no-usage-statistics | https://github.com/ChromeDevTools/chrome-devtools-mcp#usage-statistics | 2026-10-22 |
| Hardware | Partial | Needs Node.js LTS, npm and current stable Chrome on the same machine; no RAM or CPU figures documented | https://github.com/ChromeDevTools/chrome-devtools-mcp#requirements | 2026-10-22 |
| Operating systems | Confirmed | Windows, macOS and Linux wherever current Chrome runs; in WSL, Chrome must be installed inside Linux or reached on the Windows side via --browser-url | https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md | 2026-10-22 |
| Setup effort | Confirmed | Easy; add npx chrome-devtools-mcp@latest to your MCP client's config (Node.js LTS and current Chrome) | https://github.com/ChromeDevTools/chrome-devtools-mcp#requirements | 2026-10-22 |


---
Source: RepoQuarry (https://repoquarry.dev/projects/chrome-devtools-mcp). Data licence: CC BY 4.0. Quotes are from project documentation and belong to their authors.