ChromeDevTools/chrome-devtools-mcp
Chrome DevTools MCP gives coding agents direct access to browser automation, network data, console errors, screenshots, and performance traces, with privacy controls worth setting explicitly.
Google’s **Chrome DevTools MCP** connects coding agents to a live browser for automation, console and network inspection, screenshots, source-mapped errors, and performance traces. It also offers a CLI and a reduced **--slim** mode.
Add it when an agent needs to reproduce frontend bugs or validate its own UI changes in Chrome. Pin a version if repeatability matters, and consider blocking URLs or using a temporary profile when testing untrusted pages.
Google’s **Chrome DevTools MCP** connects coding agents to a live browser for automation, console and network inspection, screenshots, source-mapped errors, and performance traces. It also offers a CLI and a reduced **--slim** mode. Add it when an agent needs to reproduce frontend bugs or validate its own UI changes in Chrome. Pin a version if repeatability matters, and consider blocking URLs or using a temporary profile when testing untrusted pages. The server exposes browser and DevTools data to its MCP client. **Usage statistics are enabled by default**, performance analysis may query CrUX, and official support covers Google Chrome and Chrome for Testing rather than every Chromium browser.
This turns browser validation from a generic automation capability into a concrete coding-agent feedback loop: reproduce a UI issue, inspect runtime evidence, make a change, and verify it in Chrome. It also narrows safe adoption with explicit browser support, profile and URL controls, exposed DevTools data, default telemetry, and optional CrUX queries.