chrome-devtools-mcp config file support
Introduced 2026-09-23 · score 0.96
HOW TO USE IT
When configuring chrome-devtools-mcp for a repository workflow, put the desired server options in a JSON object and pass its path with `--config` when starting the server.
npx -y chrome-devtools-mcp@1.10.0 --config <path-to-config.json>{"headless":true,"categoryInput":false,"blockedUrlPattern":["https://example.com/*"]}WHY THIS HELPS
Configure chrome-devtools-mcp for a repository's development workflow.
REQUIREMENTS AND LIMITATIONS
- Version: 1.10.0
- --config <path> (required): Path to a JSON configuration file; the file must contain a JSON object.
- headless: Boolean; run Chrome without a UI.
- categoryInput: Boolean; set to false to exclude input tools.
- blockedUrlPattern: Array of URL patterns to block for browser network access.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v1.10.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v1.10.0/docs/configuration.md
- https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/314a5fabfec56f3067c8bd754a945e9e76bea4fb
Check the installed version and the source before using it. Entry JSON