Chrome DevTools MCP
About
Official Chrome DevTools MCP server for controlling and inspecting a live Chrome browser from coding agents such as Gemini, Claude, Cursor, and Copilot.
Details
- Author
- chromedevtools
- Categories
- Developer Tools, Automation, Other
Jump to
Setup
Install Chrome DevTools MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/chromedevtools/chrome-devtools-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
What can you do with Chrome DevTools MCP?
- Performance tracing— Ask your assistant to record a trace withperformance_start_traceand analyze insights like Core Web Vitals for any page.
- Network debugging— Uselist_network_requestsandget_network_requestto inspect failed requests, status codes, and response details.
- Console monitoring— Checklist_console_messagesfor errors and warnings with source-mapped stack traces to debug issues.
- Page automation— Direct your assistant tonavigate_page,click,fill_form, ortake_screenshotto interact with and capture live pages.
- Memory analysis— Enable memory debugging to take and compare heap snapshots, query objects, and trace retaining paths for leaks.
- Lighthouse audits— Runlighthouse_auditto get performance, accessibility, and SEO scores for a URL.
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. A[CLIis also provided for use without MCP.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
