chrome-devtools-mcp can selectively ignore default Chrome launch arguments
Introduced 2026-01-15 · score 0.90
HOW TO USE IT
When the MCP server launches Chrome and you need to omit selected Puppeteer default flags, repeat `--ignore-default-chrome-arg` for each flag to ignore. The option does not apply when connecting to an already running Chrome.
{"mcpServers":{"chrome-devtools":{"command":"npx","args":["-y","chrome-devtools-mcp@0.13.0","--ignore-default-chrome-arg=--enable-automation","--ignore-default-chrome-arg=--disable-extensions"]}}}WHY THIS HELPS
When debugging or testing requires Chrome to launch without selected Puppeteer defaults, configure chrome-devtools-mcp with the arguments to ignore.
BEFORE THIS CHANGE
There was no way to opt out of Puppeteer's default Chrome launch arguments.
REQUIREMENTS AND LIMITATIONS
- Version: 0.13.0
- --ignore-default-chrome-arg / --ignoreDefaultChromeArg: Array option; explicitly disables selected default Chrome arguments. Only applies when chrome-devtools-mcp launches Chrome. Repeat for each argument to ignore.
- Prerequisite: Node.js v20.19 or newer maintenance LTS, Chrome current stable or newer, and npm.
- Only applies when Chrome is launched by chrome-devtools-mcp.
- The option is an array and allows selectively ignoring specific default Chrome launch arguments.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.13.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/729
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/9a51af219fc9216cd463bef9363716283f41f36a/README.md
Check the installed version and the source before using it. Entry JSON