Chrome DevTools MCP
About
The official MCP server from the Chrome DevTools team. Lets agents debug a live Chrome browser: performance tracing, network request analysis, console debugging and page automation in one.
Our Verdict
Chrome DevTools MCP brings browser capabilities to the MCP ecosystem. Its GitHub popularity reflects community trust, and the standardized protocol ensures broad compatibility across AI clients.
Pricing
Use Cases
- Integrating browser capabilities into AI agent workflows
- Building custom AI-powered tools with Chrome DevTools MCP
- Enhancing AI agent functionality with standardized MCP access
Pros
- Chrome DevTools MCP provides standardized MCP protocol access
- Open source with 48,282 GitHub stars
- Active development and community support
Cons
- Requires MCP-compatible client (Claude, Cursor, etc.)
- Setup complexity varies by client
- Some features may depend on client capabilities
Installation
npx -y chrome-devtools-mcp@latestFrequently Asked Questions
What is Chrome DevTools MCP best suited for?
It exposes Chrome DevTools capabilities to AI: performance tracing, network request analysis, console log reading, Lighthouse audits and page debugging. Especially useful for hunting front-end bugs and optimizing performance.
How do I install Chrome DevTools MCP?
Just run npx -y chrome-devtools-mcp@latest — Chrome must be installed on your machine. Add this command to the MCP configuration of Claude Code, Cursor, VS Code or any other client.
Does Chrome DevTools MCP require payment or an API key?
No. Maintained by the Google Chrome DevTools team and open source under Apache-2.0, it drives your local Chrome directly — zero cost, zero keys.