Chrome DevTools MCP
Google's official MCP server that exposes Chrome DevTools to an AI agent, through around sixty tools as of 13 September 2026: performance traces, console messages with source-mapped stack traces, network requests, screenshots, Lighthouse audit, device emulation. The agent navigates, inspects the real rendered state of the page and reasons on it instead of guessing from static code. They range from input and navigation to memory, through performance, network, extensions and installable web apps.
Strengths
- Official Google, maintained by the Chrome DevTools team: solid longevity
- Over fifty tools covering perf, network, console, screenshots, device emulation, and Lighthouse
- The agent sees the real rendered state with source-mapped stack traces, not a guess from code
Limitations
- Only Google Chrome and Chrome for Testing are officially supported: another Chromium browser stays outside the contract
- Data leak risk if attached to an authenticated or sensitive tab
Best for
- Giving a front-end agent eyes in the browser for the code then verify UI loop
- Performance and network diagnosis of a page directly from Claude Code, without a Playwright suite to maintain