You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -350,20 +350,20 @@ The Chrome DevTools MCP server supports the following configuration option:
350
350
351
351
<!-- BEGIN AUTO GENERATED OPTIONS -->
352
352
353
-
-**`--autoConnect`**
353
+
-**`--autoConnect`/ `--auto-connect`**
354
354
If specified, automatically connects to a browser (Chrome 145+) running in the user data directory identified by the channel param. Requires remote debugging being enabled in Chrome here: chrome://inspect/#remote-debugging.
355
355
-**Type:** boolean
356
356
-**Default:**`false`
357
357
358
-
-**`--browserUrl`, `-u`**
358
+
-**`--browserUrl`/ `--browser-url`, `-u`**
359
359
Connect to a running, debuggable Chrome instance (e.g. `http://127.0.0.1:9222`). For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp#connecting-to-a-running-chrome-instance.
360
360
-**Type:** string
361
361
362
-
-**`--wsEndpoint`, `-w`**
362
+
-**`--wsEndpoint`/ `--ws-endpoint`, `-w`**
363
363
WebSocket endpoint to connect to a running Chrome instance (e.g., ws://127.0.0.1:9222/devtools/browser/<id>). Alternative to --browserUrl.
364
364
-**Type:** string
365
365
366
-
-**`--wsHeaders`**
366
+
-**`--wsHeaders`/ `--ws-headers`**
367
367
Custom headers for WebSocket connection in JSON format (e.g., '{"Authorization":"Bearer token"}'). Only works with --wsEndpoint.
368
368
-**Type:** string
369
369
@@ -372,15 +372,15 @@ The Chrome DevTools MCP server supports the following configuration option:
If specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed. Defaults to false.
381
381
-**Type:** boolean
382
382
383
-
-**`--userDataDir`**
383
+
-**`--userDataDir`/ `--user-data-dir`**
384
384
Path to the user data directory for Chrome. Default is $HOME/.cache/chrome-devtools-mcp/chrome-profile$CHANNEL_SUFFIX_IF_NON_STABLE
385
385
-**Type:** string
386
386
@@ -389,37 +389,37 @@ The Chrome DevTools MCP server supports the following configuration option:
389
389
-**Type:** string
390
390
-**Choices:**`stable`, `canary`, `beta`, `dev`
391
391
392
-
-**`--logFile`**
392
+
-**`--logFile`/ `--log-file`**
393
393
Path to a file to write debug logs to. Set the env variable `DEBUG` to `*` to enable verbose logs. Useful for submitting bug reports.
394
394
-**Type:** string
395
395
396
396
-**`--viewport`**
397
397
Initial viewport size for the Chrome instances started by the server. For example, `1280x720`. In headless mode, max size is 3840x2160px.
398
398
-**Type:** string
399
399
400
-
-**`--proxyServer`**
400
+
-**`--proxyServer`/ `--proxy-server`**
401
401
Proxy server configuration for Chrome passed as --proxy-server when launching the browser. See https://www.chromium.org/developers/design-documents/network-settings/ for details.
0 commit comments