Chrome DevTools MCP server
io.github.Async23/chrome-devtools-mcp·v1.7.0MCP server for Chrome DevTools
0 stars72 downloads/wk
Reviews
Write oneNobody has reviewed Chrome DevTools MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Chrome DevTools MCP tools (2, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
execute_3p_developer_toolwrite actionExecutes a tool exposed by the page.
list_3p_developer_toolsLists all third-party developer tools the page exposes for providing runtime information. Third-party developer tools can be called via the 'execute_3p_developer_tool()' MCP tool. Alternatively, third-party developer tools can be executed by calling 'evaluate_script' and adding the following command to the script: `window.__dtmcp.executeTool(toolName, params)` This might be helpful when the third-
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- Code scan75 source files scanned15/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 41 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumeval / new Function used
exec.evalbuild/src/third_party/devtools-formatter-worker.js: …is.e = e; this.f = f; } eval(val) { const sign = val < 0 ? -1… - mediumGoogle API key in source (often public by design; check its restrictions)
secret.googlebuild/src/tools/performance.js: …ogleapis.com/v1/records:queryRecord?key=AIza****'); const cruxSetting = DevTools.Com…
How Chrome DevTools MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 72/100
- higher than 38% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 50%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 72
- more than 55% of 12,191 servers with a package
What its tools let an agent do: 1 read · 1 run or deploy
Install Chrome DevTools MCP in Claude Code, Cursor or VS Code
Runs npx -y @async23/chrome-devtools-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add chrome-devtools-mcp -- npx -y @async23/chrome-devtools-mcp
What the publisher says
From the Chrome DevTools MCP repository's README, as published. We do not edit it. Read it on GitHub
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 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.
This repository publishes the Async23 fork as @async23/chrome-devtools-mcp. It includes the local visible-browser focus control and oversized full-page screenshot fixes while retaining the chrome-devtools-mcp executable name.
Tool reference | Changelog | Contributing | Troubleshooting | Design Principles
Key features
DevTools](https://github.com/ChromeDevTools/devtools-frontend) to record traces and extract actionable performance insights.
- Get performance insights: Uses [Chrome
check browser console messages (with source-mapped stack traces).
- Advanced browser debugging: Analyze network requests, take screenshots and
puppeteer to automate actions in Chrome and automatically wait for action results.
- Reliable automation. Uses
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", "@async23/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 CHROMEDEVTOOLSMCPNOUSAGE_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 CHROMEDEVTOOLSMCPNOUPDATE_CHECKS environment variable.
Requirements
- Node.js LTS version.
- Chrome current stable version or newer.
- npm
Getting started
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Chrome DevTools MCP: common questions
- Is Chrome DevTools MCP server safe?
- Mostly: it is graded B (72/100). Read the Chrome DevTools MCP safety report
- How do I install Chrome DevTools MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Chrome DevTools MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Chrome DevTools MCP maintained?
- The last commit was 41 days ago (2026-09-24). The latest release is v1.7.0.
- How does Chrome DevTools MCP compare with other MCP servers?
- safety score 72/100 (higher than 38% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.