Why you'd want it
It gives an agent the parts of Chrome DevTools a developer reaches for: recording performance traces with extracted insights, inspecting network requests, reading console messages with source-mapped stack traces and taking screenshots. Automation runs on Puppeteer and waits for action results automatically. A --slim mode trims the tool set for basic browser tasks, and a separate CLI works without MCP.
Best for
- Debugging front-end bugs with an agent
- Performance analysis of web pages
- Checking console and network errors after a code change
Use it when
You want your coding agent to check its changes in a real Chrome instance, reading console, network and performance data the way you would in DevTools.
Skip it if
You need Firefox or WebKit; only Chrome and Chrome for Testing are officially supported. Usage statistics go to Google by default (opt out with --no-usage-statistics), and performance tools may send trace URLs to the CrUX API unless you pass --no-performance-crux.
Editor's note
The README now titles the project "Chrome DevTools for agents"; the npm package is still chrome-devtools-mcp.