chrome-devtools-mcp: A Chinese Translation That Cuts the Setup Reading Time
The original chrome-devtools-mcp repository has 58377 stars and a README that runs several screens long. For a Chinese-speaking developer who just wants an AI agent to open a page and record a trace, that length is the f
The original chrome-devtools-mcp repository has 58377 stars and a README that runs several screens long. For a Chinese-speaking developer who just wants an AI agent to open a page and record a trace, that length is the first obstacle. A translation of the project went up on 2026-11-20 at yangshun2005/chrome-devtools-mcp-cn, and its main contribution is not new code β it is a shorter path from "what is this" to "it is running."
The project is a Model-Context-Protocol server plus a CLI. It lets coding agents such as Antigravity, Claude, Cursor, or Copilot control and inspect a live Chrome browser. Under the hood it sits on Chrome DevTools and puppeteer, so the agent gets performance tracing, network inspection, screenshots, and console message reading with source map stack traces. Language is TypeScript, license Apache-2.0.
What the Chinese version actually contains
Two layers, and the repo is explicit about the split.
The top section is labeled γδΈζεΏ«ιδΈζγ and marked as supplementary β not part of the original document. It exists so you do not have to read the whole README before the first run. Below that, the body is a translation of the upstream README, with the stated goal of staying faithful to the original. The English source is kept alongside as README_en.md.
That structure matters. A pure translation still forces you to read everything in order. A translation with a short onboarding layer on top lets you stop reading once the browser opens.
The translation date is 2026-11-20. If the upstream README changes after that, the Chinese copy will lag until someone updates it. The repo asks for Issues or PRs on inaccurate translations, which is the honest way to handle drift.
The minimum config is four lines of JSON
The quick-start section leads with the config block, because that is where most people get stuck:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
Prerequisites are Node.js LTS, npm, and Chrome at the current stable version or newer. Editor-specific setup is deferred to the Client Configurations Guide under docs/ β the translated README does not name the exact file, and it says so rather than guessing.
Verification is one prompt typed into the MCP client:
Check the performance of https://developers.chrome.com
If the client is wired up correctly, a browser opens and a performance trace gets recorded.
One behavior that trips people up
Connecting the MCP server does not launch a browser. The browser only starts when the client calls a tool that needs one. Anyone who configures the server, sees no window appear, and assumes the setup failed is reading the situation wrong. The Chinese quick-start calls this out in a standalone note; it is the kind of detail that is easy to bury inside a long English README.
CLI path when you skip MCP entirely
Not every task needs an agent in the loop. The original documents a terminal route:
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
The numeric argument is a page identifier. Navigate, capture, stop. Useful for scripted checks where spinning up a full MCP client is overhead.
Defaults worth turning off before you trust it
The translated README keeps the original's warnings, and they are not decorative.
Data exposure. The server exposes the contents of the browser instance to the MCP client. The client can inspect, debug, and modify any data in the browser or DevTools. Do not point it at a profile holding sensitive or personal information.
Usage statistics are on by default. Google collects tool call success rates, latency, and environment information. Turn it off with --no-usage-statistics, or set CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI.
Performance tools can send data outward. Trace URLs may go to the Google CrUX API to pull real-user experience data, which lets field data sit next to lab data. Disable with --no-performance-crux.
Update checks run periodically. The server polls npm and prompts when a newer version exists. Set CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS to stop it.
Browser support is narrow. Only Google Chrome and Chrome for Testing are officially supported. Other Chromium-based browsers may work but are not guaranteed and can behave unexpectedly. Fixes and support are committed for the latest Extended Stable Chrome.
Where the translation earns its place
Three concrete gains for a Chinese-speaking developer.
First, the privacy and telemetry warnings land in the reader's first language at the moment they configure the tool, not after they have already pointed it at a logged-in profile. Default-on usage statistics and CrUX trace uploads are exactly the sort of thing people skim past in a second language.
Second, the quick-start separates "run it" from "understand it." The original README is organized as reference material β tool reference, CLI, skills, changelog, contributing, troubleshooting, design principles. That is the right shape for a project with 58377 stars and a wide audience. It is the wrong shape for someone evaluating the tool in ten minutes.
Third, the environment requirements are stated plainly: Node.js LTS, npm, Chrome stable or newer. The translated version also adds a note the original does not make β npm installs may need a mirror or download acceleration on mainland networks. That is a practical addition, flagged as such rather than passed off as original content.
One gap: the translated README does not specify supported operating systems or hardware requirements, and it says the original does not either. No invented compatibility matrix.
What this repo is not
It is not a fork with patches. It is not a mirror that tracks upstream commits automatically. The stars count belongs to ChromeDevTools/chrome-devtools-mcp at 58377; the Chinese version is new as of 2026-11-20 and has no track record yet. If you need the canonical source of truth for behavior, read the English README and the upstream code. The translation is a reading aid, and treating it as anything more will mislead you the first time upstream changes something.
I have not benchmarked the setup time difference between the two READMEs β that claim would need actual measurement, and this piece does not make it. What can be said without measurement: the Chinese version front-loads the config block, the verification prompt, and the five default behaviors that need disabling, before the translated reference material begins.
When to reach for it
If your team reads Chinese and your agent stack includes Chrome automation, the translated quick-start gets you to a working trace in one config paste and one prompt. If you are debugging an unexpected tool behavior, go upstream β the translation will not have answers the original lacks, and it may be behind.
Repo: https://github.com/yangshun2005/chrome-devtools-mcp-cn. Original: https://github.com/ChromeDevTools/chrome-devtools-mcp.
Chinese documentation: https://github.com/yangshun2005/chrome-devtools-mcp-cn
I'm an independent enterprise AI delivery consultant β private LLM deployment, RAG, agent workflows, AIOps. If your team is stuck somewhere in that stack, my inbox is open.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.