Chrome DevTools MCP
Google's official MCP server that exposes the 29 Chrome DevTools tools to an AI agent: 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. Seven tool categories: input, navigation, performance, network, debugging, emulation, memory.
Strengths
- Official Google, maintained by the Chrome DevTools team: solid longevity
- 29 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
- Requires a Chrome instance launched with the debug port: no trivial 100% headless CI
- 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