chrome-devtools-mcp
Chrome DevTools for coding agents
- 评测生成时间(北京时间)
- 本报告引擎
- v3.8.0
- 当前引擎
- v3.17.3
本报告与当前引擎使用不同规则;原分数不会自动更新,不同版本的分数不宜直接对比。
进入后确认来源与额度,提交才会创建任务。
代码版本未记录或记录无效,无法核对本报告的 commit 与送评文本;不会用当前项目代码回填历史记录。
综合采用结论
证据充分,整体质量与安全表现优秀
- 基础评测完成+25/25确定性评分与静态安全扫描已完成
- README 有效证据+25/2533,404 个去重后的有效字符
- 独立证据来源+12/203 类非重复证据,重复文件不叠加
- 仓库元数据+10/10已取得仓库状态与采用数据
- 活跃记录+5/5已取得最近提交时间
- AI 复核+15/15已完成结构化 AI 证据复核
本报告评了什么
综合分用于静态采用筛选,不是任务成功率,也不代表使用 Skill 后的能力提升。
- 静态检查范围
- 记录 3 个文件 · 58,362 字符
- 只检查采集到的受限文本与已知风险模式;未读取的脚本、依赖和运行环境不在结论内。
- AI 内容复核
- 已使用
- 复核送评文本的说明和设计,不是安装测试或实际任务执行。记录缺失时不推断已使用或未使用。
- 真实任务效果
- 本报告未提供实测证据
- 没有使用/不使用 Skill 的任务对照、重复运行或耗时与 token 成本结果。采用前仍需在隔离环境验证自己的任务。
脚本引用覆盖
脚本引用覆盖记录不可得;不推断没有引用或已经检查。
MCP服务器与浏览器交互流程
README展示了MCP客户端配置、服务器启动、浏览器连接及工具调用,存在请求-响应关系。
左右滑动查看完整图示
- • 配置示例:mcpServers.chrome-devtools.command = npx
- • 自动连接:--autoConnect 连接运行中的Chrome
- • 工具调用:如navigate_page, take_screenshot等
- 工具列表:Input automation (10 tools), Navigation automation (6 tools), Debugging (8 tools), Memory (13 tools)等
- 配置选项:--slim, --isolated, --blockedUrlPattern, --allowedUrlPattern, --redactNetworkHeaders
- 客户端配置:Claude Code CLI命令`claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest`
- 自动连接步骤:chrome://inspect/#remote-debugging 和 --autoConnect
- 限制声明:--categoryExtensions 仅支持pipe连接,--categoryPwa 不支持autoConnect等
- 有效 README
- 安装或接入步骤
- 可执行示例
- 输入、参数或工具说明
- 未发现已知高风险模式
- 缺少问题与用途描述
- 缺少许可证信息
- 部分功能(如扩展、PWA)仅支持pipe连接,限制使用场景
- 实验性功能(如vision、screencast)需要额外依赖或标志
- 未提供错误处理或排障的具体示例
需要浏览器自动化与调试的AI编码代理、需要性能分析与内存快照的开发者、需要多客户端统一浏览器控制的环境、需要安全网络限制(URL模式)的场景
需要扩展或PWA自动化且使用非pipe连接的用户、需要稳定无实验性功能的简单浏览器任务(可考虑--slim)
也有自己的公开项目?先免登录查已有报告;没有报告时,可保留地址继续登录评测。
查找我项目的报告 →静态扫描不是安全保证,生产接入前仍应人工复核权限和数据边界。
- 01补充问题与用途描述
- 02补充许可证信息
方法、证据与局限展开收起
GitHub Repository API
3 个文件 · 58,362 字符
v3.8.0 · AI 内容复核:已使用(deepseek-chat)
- 静态评测不会安装或执行项目代码
- 安全扫描基于高信号文件与已知模式,不能替代人工审计
- 流行度只反映采用程度,不代表安全或工程质量
30 天热度趋势
README
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. 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 | CLI | Skills | Changelog | Contributing | Troubleshooting | Design Principles
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:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
[!NOTE] Using
chrome-devtools-mcp@latestensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
MCP Client configuration
For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our Client Configurations Guide.
Your first prompt
Enter the following prompt in your MCP Client to check if everything is working:
Check the performance of https://developers.chrome.com
Your MCP client should open the browser and record a performance trace.
[!NOTE] The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.
CLI
The package also includes the chrome-devtools CLI. Use it to control the browser from your terminal without MCP:
npm i chrome-devtools-mcp@latest -g
chrome-devtools navigate_page 1 --url "https://developers.chrome.com"
chrome-devtools take_screenshot 1 --filePath screenshot.png
chrome-devtools stop
See the CLI guide for all commands and options.
Skills
The package includes skills that teach your agent how to use Chrome DevTools:
| Skill | Use it to |
|---|---|
chrome-devtools | Debug and automate pages with the MCP tools. |
chrome-devtools-cli | Run the CLI and write shell scripts with it. |
a11y-debugging | Audit and fix accessibility issues. |
cookie-debugging | Debug cookies, sessions, and authentication. |
debug-optimize-lcp | Debug and improve Largest Contentful Paint. |
memory-leak-debugging | Find and fix memory leaks. |
troubleshooting | Fix connection problems between MCP and Chrome. |
Install skills as a plugin
A plugin installs the MCP server and all skills, including the CLI skill:
- Claude Code: Run
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp, then/plugin install chrome-devtools-mcp@chrome-devtools-plugins. - Copilot / VS Code: Run Chat: Install Plugin From Source and enter
ChromeDevTools/chrome-devtools-mcp. - Gemini CLI: Run
gemini extensions install --auto-update https://github.com/ChromeDevTools/chrome-devtools-mcp.
See the Client Configurations Guide for more information.
Install skills manually
If your agent does not support plugins, copy the skill folders into the skills directory of your agent. The npm package contains the skills:
npm i chrome-devtools-mcp@latest -g
# Example for Claude Code. Use the skills directory of your agent.
mkdir -p ~/.claude/skills
cp -R "$(npm root -g)/chrome-devtools-mcp/skills/chrome-devtools-cli" ~/.claude/skills/
[!IMPORTANT] The
chrome-devtools-cliskill requires the CLI. Install the package globally before you use the skill.
Keep skills up to date
Skills describe the tools of a specific version. Update the skills each time you update the MCP server or the CLI. Outdated skills can tell your agent to use tools or parameters that changed.
- Plugins: Use the update command of the plugin manager of your agent. The Gemini CLI command above enables automatic updates with
--auto-update. - Manual installs: Update the package, then copy the skill folders again:
npm i chrome-devtools-mcp@latest -g
mkdir -p ~/.claude/skills
cp -R "$(npm root -g)/chrome-devtools-mcp/skills/chrome-devtools-cli" ~/.claude/skills/
Tools
If you run into any issues, checkout our troubleshooting guide. See the full Tool Reference for a complete list of all supported MCP capabilities.
Configuration
Find the complete list of server parameters (e.g., --headless, --isolated, --slim) and how to configure WebSocket connections in the Configuration Guide.
For basic browser tasks only, the --slim flag exposes a reduced set of tools. See the Slim tool reference.
Advanced Usage
For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Chrome instance instead of starting a new one, or debugging on Android, see our Advanced Usage Guide.
Integrating as a browser subagent
If you are developing agentic tooling and want to provide an integrated browser subagent as part of your product, we recommend building on top of Chrome DevTools for agents.
For a reference implementation, see the Gemini CLI browser agent documentation.