MCP server that lets coding agents control and inspect a live Chrome browser via DevTools.
MCP server that lets coding agents control and inspect a live Chrome browser via DevTools.
Chrome DevTools for agents
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 is available as a
Model-Context-Protocol (MCP) server and as a [CLI][cli]. Both give your AI
coding assistant access to the full power of Chrome DevTools for reliable
automation, in-depth debugging, and performance analysis.
[Tool reference][tool-reference] | [CLI][cli] | [Skills][skills] | [Changelog][changelog] | [Contributing][contributing] | [Troubleshooting][troubleshooting] | [Design Principles][design-principles]
• Get performance insights: Uses Chrome
DevTools to record
traces and extract actionable performance insights.
• Advanced browser debugging: Analyze network requests, take screenshots and
check browser console messages (with source-mapped stack traces).
• Reliable automation. Uses
puppeteer to automate actions in
Chrome and automatically wait for action results.
chrome-devtools-mcp exposes content of the browser instance to the MCP clients
allowing them to inspect, debug, and modify any data in the browser or DevTools.
Avoid sharing sensitive or personal information that you don't want to share with
MCP clients.
chrome-devtools-mcp officially supports Google Chrome and Chrome for Testing only.
Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior. Use at your own discretion.
We are committed to providing fixes and support for the latest version of Extended Stable Chrome.
Performance tools may send trace URLs to the Google CrUX API to fetch real-user
experience data. This helps provide a holistic performance picture by
presenting field data alongside lab data. This data is collected by the Chrome
User Experience Report (CrUX). To disable
this, run with the --no-performance-crux flag.
Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.
Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:
"args": ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]
Google handles this data in accordance with the Google Privacy Policy.
Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.
Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.
By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available.
You can disable these update checks by setting the CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.
• Node.js LTS version.
• Chrome current stable version or newer.
• npm
Add the following config to your MCP client: …
MCP server · MCP servers / Browser automation · Open Source · Apache-2.0 · TypeScript
Website https://developer.chrome.com/docs/devtools/agents · Repo https://github.com/ChromeDevTools/chrome-devtools-mcp · Docs https://developer.chrome.com/docs/devtools/agents
55,124 stars · 4,589 forks · 121 open issues · pushed 2026-11-12 · verified 2026-11-12
Tags: ai-agents, mcp-server, browser-automation
What is Chrome DevTools MCP? Chrome DevTools MCP is a coding tool listed on Scriptiii AI Tools. MCP server that lets coding agents control and inspect a live Chrome browser via DevTools. Pricing: Free. Free to use. Best for: ai-agents, mcp-server, browser-automation.
Everything you need to know about Chrome DevTools MCP
Similar tools in Coding
Open-source vector database that stores objects and vectors with hybrid search and filtering.
Coding·Free