Chrome DevTools MCP Gives Agents 63 Tools and Sends Usage Statistics by Default
Software / news
Chrome DevTools MCP Gives Agents 63 Tools and Sends Usage Statistics by Default
The repository's own README, not the launch post, is where the data-collection default and the opt-out flags are written down.
Chrome DevTools MCP, the server that lets coding agents drive a live Chrome browser, has 57.0k stars on GitHub, 63 tools and usage-statistics collection switched on by default. The setting appears in the README, not in the Sept. 23, 2025 launch post that introduced the project.
That post, written by Mathias Bynens and Michael Hablich, describes agents that record performance traces, check network requests and read console logs. It names one tool, performance_start_trace, and says nothing about privacy or data handling, according to the page as fetched on Nov. 16.
What the README says about data
The ChromeDevTools/chrome-devtools-mcp repository is Apache-2.0 licensed and lists 95 open issues and 40 open pull requests. Its disclaimers section makes four separate statements.
- Content exposure: the server "exposes content of the browser instance to the MCP clients," and users should "avoid sharing sensitive or personal information that you don't want to share with MCP clients."
- Usage statistics: "Data collection is enabled by default." The flag
--no-usage-statisticsturns it off, and collection stops on its own when theCIenvironment variable is set. - CrUX lookups: performance tools "may send trace URLs to the Google CrUX API" to fetch real-user data. The flag
--no-performance-cruxdisables that. - Update checks: the server periodically asks the npm registry for a newer version. Setting
CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKSstops it.
The README does not say, on the page fetched, exactly which fields the usage statistics contain.
What 63 tools can reach
The tool reference counts 63 tools in 13 categories. Memory and input automation account for 24 of them.
- Memory14 tools
- Input automation10 tools
- Debugging10 tools
- Navigation automation6 tools
- Extensions5 tools
- Progressive Web Apps4 tools
- Performance3 tools
- Network2 tools
Source: ChromeDevTools/chrome-devtools-mcp docs/tool-reference.md, accessed 2026-11-16
Two of them matter most for the privacy warning. evaluate_script runs JavaScript in the target page or service worker. get_network_request returns request and response bodies, inline or saved to a file.
A response body from a logged-in session is the sort of content the disclaimer is describing. The README's advice is to use a browser profile that holds nothing you would not hand to the agent.
Who is affected
The README names Antigravity, Claude, Cursor and Copilot as clients, and its configuration guide also covers Claude Code, VS Code and Gemini CLI. It requires Node.js LTS and current stable Chrome. A --slim flag exposes a reduced tool set.
Anyone who added the server to a client config from a tutorial inherits all three defaults: statistics on, CrUX lookups on, update checks on. A team running it in CI is exempt from the statistics only.
Google's Modern Web Guidance project ships through the same coding-agent channel, and Agweb takes a different route to giving agents a browser. Neither changes what this server reports.
The repository's Releases section is empty, so there is no tagged version to pin against. The fixed point is the flag list: three opt-outs, to be added to the server's launch arguments or environment before it touches a browser profile.
Sources
More in Software
- 01Zigzag, a 35 MB Mac Browser, Courts Arc Users 35 Days Before ShutdownThe WebKit-based browser imports Arc spaces and pinned tabs, but its README lists no sync, no Boosts and a partial Chrome extension API.
- 02Nimony 0.6.2 Sets a Year-End Goal for Nim 3 With 44 Days LeftThe compiler that will become Nim 3 is MIT-licensed and builds natively without LLVM, but its FAQ says it cannot yet compile Nim 2 code unchanged.
- 03Alloy CSS Runs Menus and Tabs Without JavaScript, but Dialogs Need Safari 26.2The 24 KB MIT stylesheet leans on popover and invoker commands, so its no-script promise has browser floors that differ by component.
- 04Windows 11 Telemetry Flags Which Coding Agents You Run, Researcher FindsXusheng Li traced a service-experiment feature in build 26200.9974 that matches executable names such as claude.exe and queues the result as optional diagnostic data.