Chrome DevTools
Chrome DevTools MCP hands an agent a real, running Chrome instance: puppeteer-driven actions plus DevTools-grade network, console, and performance-trace inspection.
Add to Claude Code
claude mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
Source: https://github.com/ChromeDevTools/chrome-devtools-mcp
About
This is Google's official MCP server for Chrome DevTools, and it goes further than a typical browser-automation server: alongside puppeteer-driven actions (click, fill_form, navigate_page, upload_file), it exposes DevTools-native inspection, including recording and analyzing performance traces, listing network requests, reading console messages with source-mapped stack traces, and running Lighthouse audits, all against one live browser session an agent can act on and inspect in the same turn.
The tool set is organized by category (input, navigation, emulation, performance, network, debugging, memory, extensions, and PWA install/launch) and numbers in the fifties altogether, enough surface area to cover most real debugging and QA workflows without leaving the assistant. It works with Claude, Cursor, Copilot, and Antigravity, and a standalone CLI is available for running the same automation outside an MCP client entirely.
Key features
- Puppeteer-backed automation: click, fill_form, drag, navigate_page, upload_file, and more
- Performance tracing and analysis via performance_start_trace/performance_analyze_insight
- Network inspection (list_network_requests, get_network_request) and console reading with source-mapped stack traces
- Lighthouse audits and full-page screenshots/screencasts for visual verification
- Chrome extension management (install/list/reload/uninstall) and PWA install/launch tools
- Emulation tools for resizing the viewport or emulating device/network conditions
Use cases
- Debugging a failing UI flow by having the agent click through it and read the resulting console/network activity
- Running a performance trace and asking the agent to explain what's slow, backed by real DevTools data
- Automating repetitive QA checks (form fills, navigation flows) against a live page instead of a mocked one
- Auditing a page with Lighthouse and having the agent triage which findings are worth fixing first
Available tools
navigate_page
Navigates the current browser tab to a given URL.
take_screenshot
Captures a screenshot of the current page or a specific element.
performance_start_trace
Starts recording a Chrome DevTools performance trace.
list_network_requests
Lists network requests made by the page, for inspecting API calls or asset loads.
evaluate_script
Runs arbitrary JavaScript in the context of the current page.
Frequently asked questions
Does it control my regular Chrome profile?
It launches and controls a Chrome instance via Puppeteer, which by default is a fresh automated instance rather than your everyday browsing profile, though it can be pointed at an existing debug-enabled Chrome.
Can I use it without an MCP client?
Yes. The project also ships a standalone CLI that drives the same DevTools automation directly, for cases where you don't want to go through an MCP client.