← MCP

Chrome DevTools MCPChrome DevTools MCP

Google（Chrome DevTools 团队）Google (Chrome DevTools team)

MCPMCP 浏览器调试Browser debugging CDPCDP Apache2.0Apache2.0 本地stdioLocal stdio 性能分析Performance analysis partial lifecycle: active 核验Checked 2026-10-30

Chrome 官方团队做的「让 agent 看见浏览器」：CDP 直连，导航、交互、截图、performance trace、网络与 console 全暴露给编码 agent。Apache-2.0、53k★、活跃维护。安全口径一句话：它驱动真实浏览器=真实网络出口，server 本身没有 URL 白名单层。

Chrome's own team built 'let the agent see the browser': direct CDP — navigate, interact, screenshot, performance traces, network and console. Apache-2.0, 53k stars, active. Security in one line: it drives a real browser with a real network exit, and the server itself has no URL allowlist layer.

适合与不适合When to use it, when not to

适合：编码 agent 的「改代码→浏览器验证」闭环、性能诊断、E2E 调试。不适合：批量抓取（fetch/firecrawl 更合适）；要 URL 级硬隔离的场景。

Fits: the coding agent's 'edit code → verify in browser' loop, performance diagnosis, E2E debugging. Not a fit: bulk scraping (fetch/firecrawl fit better); scenarios needing hard URL-level isolation.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Google（Chrome DevTools 团队）。Google (Chrome DevTools team).
国内使用Direct access: 直连不可达direct blocked　github.com 直连实测 000（波动，同日代理可达 200）。github.com measured 000 direct (fluctuating; 200 via proxy the same day).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；开源项目未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the open-source project does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它把 Chrome DevTools 协议（CDP）能力包装成工具：导航、点击、截图、性能 trace、网络与 console 日志。
It calls no model itself — an interface implementation called by MCP clients. It wraps Chrome DevTools Protocol (CDP) capabilities as tools: navigation, clicking, screenshots, performance traces, network and console logs.
运行位置Where it runs: 本地进程（npx 起 stdio，驱动本机 Chrome）；GitHub 54,460★，最近推送 2026-10-29（API 核验）—— MCP 生态头部流量之一。
A local process (npx starts stdio, driving the machine's Chrome); GitHub 54,460★, last push 2026-10-29 (API verified) — one of the top-traffic projects in the MCP ecosystem.
本地文件Local files: 操作的是浏览器运行时：页面、网络、console；截图/trace 可落本地路径（由参数指定）。它不读写你项目源码——那是 filesystem server 的活。
What it operates is the browser runtime: pages, network, console; screenshots/traces can be saved to local paths (specified by parameters). It does not read or write your project source code — that is the filesystem server's job.
关机后的任务Tasks after shutdown: 随客户端生死（stdio 子进程）；Chrome 实例由它启动或连接。无后台任务语义。
Lives and dies with the client (a stdio child process); the Chrome instance is launched or attached by it. No background-task semantics.
工具与扩展Tools & extensions: 导航/交互（click/type/upload）、截图、performance trace 与分析、网络与 console 读取、模拟（CPU/网络节流）等；完整清单以仓 README 为准。
Navigation/interaction (click/type/upload), screenshots, performance tracing and analysis, network and console reading, emulation (CPU/network throttling), etc.; the complete inventory follows the repo README.
上下文与记忆Context & memory: 无跨会话记忆——页面状态在浏览器实例里，会话结束实例关闭。
No cross-session memory — page state lives in the browser instance; when the session ends the instance closes.
权限与限制Permissions & limits: 它驱动一个真实浏览器：能访问客户端让它去的任何 URL、以浏览器身份交互。官方口径是给编码 agent 做「看得到浏览器」的能力；隔离与白名单靠客户端/浏览器 profile 配置—— server 本身无 URL 白名单机制的官方说明。
It drives a real browser: it can visit any URL the client tells it to and interact as the browser. The official positioning is giving coding agents the ability to "see the browser"; isolation and allowlists rely on client/browser-profile configuration — there is no official statement of a URL-allowlist mechanism in the server itself.
适合什么任务Best for: 适合：编码 agent 调试真实页面、性能分析、E2E 验证闭环（改代码→看浏览器→再改）。不适合：要无头批量抓取（那是 fetch/firecrawl 线）；要 URL 级硬隔离（server 无此机制）。
Fits: coding agents debugging real pages, performance analysis, the E2E verification loop (change code → look at the browser → change again). Not a fit: headless bulk scraping (the fetch/firecrawl line); scenarios needing URL-level hard isolation (the server has no such mechanism).
传输方式Transport: stdio（npx chrome-devtools-mcp@latest）；HTTP 模式支持状态未逐条核验。核验：仓 README（2026-10-21 直抓）。
stdio (npx chrome-devtools-mcp@latest); HTTP-mode support status not verified item by item. Verified against: the repo README (direct-fetched 2026-10-21).
认证机制Authentication: 无凭据层——它不需要账号 token，权限=浏览器实例能做的事。连接既有 Chrome 实例（--connect-to-existing-browser 一类）支持面未逐条核验。
No credential layer — it needs no account token; permissions = whatever the browser instance can do. Support for connecting to an existing Chrome instance (a --connect-to-existing-browser kind of option) not verified item by item.
权限范围Permission scope: 作用域=浏览器运行时：任意导航、交互、读网络/console、跑 performance trace。无 URL 白名单/审批层的官方说明——收紧靠客户端侧工具审批与浏览器 profile 隔离。
The scope is the browser runtime: arbitrary navigation, interaction, reading network/console, running performance traces. No official statement of a URL allowlist or approval layer — tightening relies on client-side tool approval and browser-profile isolation.

头号误解Top misconception

把它当 Playwright MCP 的替代品混用——两者重叠但机制不同（CDP 直连 vs Playwright 驱动），官方 reference 归档后推荐 Playwright 是另一条线，两者现役都活跃Using it interchangeably with Playwright MCP — overlapping but different mechanisms (direct CDP vs Playwright driver); both lines are active
忘了它驱动真实浏览器=真实网络出口——agent 让它访问什么就访问什么Forgetting that driving a real browser means a real network exit — the agent can reach whatever it is told to
把 53k★ 当「安全默认」——星数是热度，权限面要按「浏览器身份」单独评估Reading 53k stars as 'safe by default' — stars are popularity; the browser-identity permission surface needs its own assessment

未知项清单Known unknowns

HTTP 传输模式支持状态（未逐条核验）
连接既有浏览器实例的参数面（未逐条核验）
与 Playwright MCP 的能力差异矩阵（重叠区未逐条对照）

HTTP transport-mode support status (not verified item by item)
The parameter surface for attaching to an existing browser instance (not verified item by item)
The capability-difference matrix vs Playwright MCP (the overlap area not compared item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
repo	ChromeDevTools/chrome-devtools-mcp · 仓库（Apache-2.0；54,460★，最近推送 2026-10-29，GitHub API 核验）ChromeDevTools/chrome-devtools-mcp · repository (Apache-2.0; 54,460★, last push 2026-10-29, GitHub API verified)	https://github.com/ChromeDevTools/chrome-devtools-mcp
changelog	ChromeDevTools/chrome-devtools-mcp · Releases（changelog）ChromeDevTools/chrome-devtools-mcp · Releases (changelog)	https://github.com/ChromeDevTools/chrome-devtools-mcp/releases
docs	Chrome DevTools · 官方文档（CDP 能力背景）Chrome DevTools · official docs (CDP capability background)	https://developer.chrome.com/docs/devtools

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.