About this project
Chrome DevTools for agents (chrome-devtools-mcp) is an MCP server that gives AI coding assistants—such as Antigravity, Claude, Cursor, or Copilot—the ability to control and inspect a live Chrome browser. It exposes Chrome DevTools capabilities through the Model Context Protocol, enabling reliable automation, debugging, and performance analysis. A CLI is also available for use without MCP.
Key features:
- Performance insights: Records Chrome DevTools traces and extracts actionable performance information.
- Advanced browser debugging: Inspects network requests, takes screenshots, and reads browser console messages, including source-mapped stack traces.
- Reliable automation: Uses Puppeteer to automate actions in Chrome and waits for action results automatically.
Official support covers Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work but are not guaranteed. Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data; this can be disabled with the --no-performance-crux flag.
Usage statistics are collected by default to improve reliability and performance, with an opt-out via --no-usage-statistics or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI environment variables. The server also checks the npm registry for updates unless CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS is set.
Setup involves adding the package to an MCP client configuration, for example:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
A slim mode is available for basic browser tasks, and documentation covers advanced usage like concurrent sessions, persistent user data directories, connecting to a running Chrome instance, and Android debugging. The package also serves as a foundation for building integrated browser subagents in agentic tooling.
Comments
0 Rating appears after 10 ratings
Sign in to join the discussion.