Arc DevTools MCP
A fork of chrome-devtools-mcp
(Google, Apache-2.0) that adds an Arc browser compatibility mode.
Why this fork
Arc crashes when a tab is created programmatically (Target.createTarget, which
browser.newPage() triggers). Run with --arc and new_page instead reuses an
existing blank tab rather than opening one:
- Reuses a blank/new tab (
about:blank, arc://newtab, chrome://newtab/) and
loads the URL there.
- If no blank tab exists, it returns a clear error asking you to open one
(e.g.
Cmd+T) — it never navigates one of your loaded tabs away.
- Without
--arc, behavior is identical to upstream chrome-devtools-mcp.
Start Arc with remote debugging (Arc must be fully quit first):
/Applications/Arc.app/Contents/MacOS/Arc --remote-debugging-port=9222
MCP config:
{
"mcpServers": {
"arc-devtools": {
"command": "npx",
"args": ["-y", "@gabrielbryk/arc-devtools-mcp@latest", "--browserUrl=http://127.0.0.1:9222", "--arc"]
}
}
}
Everything below is from upstream chrome-devtools-mcp and applies unchanged.
Chrome DevTools for agents
Chrome DevTools for agents 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 CLI is also provided for use without MCP.
Key features
- 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.
Disclaimers
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.
Usage statistics
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.
Update checks
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.
Requirements
Getting started
Add the following config to your MCP client:
