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
@@ -353,20 +353,20 @@ The Chrome DevTools MCP server supports the following configuration option:
353
353
354
354
<!-- BEGIN AUTO GENERATED OPTIONS -->
355
355
356
-
-**`--autoConnect`**
356
+
-**`--autoConnect`/ `--auto-connect`**
357
357
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.
358
358
-**Type:** boolean
359
359
-**Default:**`false`
360
360
361
-
-**`--browserUrl`, `-u`**
361
+
-**`--browserUrl`/ `--browser-url`, `-u`**
362
362
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.
363
363
-**Type:** string
364
364
365
-
-**`--wsEndpoint`, `-w`**
365
+
-**`--wsEndpoint`/ `--ws-endpoint`, `-w`**
366
366
WebSocket endpoint to connect to a running Chrome instance (e.g., ws://127.0.0.1:9222/devtools/browser/<id>). Alternative to --browserUrl.
367
367
-**Type:** string
368
368
369
-
-**`--wsHeaders`**
369
+
-**`--wsHeaders`/ `--ws-headers`**
370
370
Custom headers for WebSocket connection in JSON format (e.g., '{"Authorization":"Bearer token"}'). Only works with --wsEndpoint.
371
371
-**Type:** string
372
372
@@ -375,15 +375,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.
384
384
-**Type:** boolean
385
385
386
-
-**`--userDataDir`**
386
+
-**`--userDataDir`/ `--user-data-dir`**
387
387
Path to the user data directory for Chrome. Default is $HOME/.cache/chrome-devtools-mcp/chrome-profile$CHANNEL_SUFFIX_IF_NON_STABLE
388
388
-**Type:** string
389
389
@@ -392,37 +392,37 @@ The Chrome DevTools MCP server supports the following configuration option:
392
392
-**Type:** string
393
393
-**Choices:**`stable`, `canary`, `beta`, `dev`
394
394
395
-
-**`--logFile`**
395
+
-**`--logFile`/ `--log-file`**
396
396
Path to a file to write debug logs to. Set the env variable `DEBUG` to `*` to enable verbose logs. Useful for submitting bug reports.
397
397
-**Type:** string
398
398
399
399
-**`--viewport`**
400
400
Initial viewport size for the Chrome instances started by the server. For example, `1280x720`. In headless mode, max size is 3840x2160px.
401
401
-**Type:** string
402
402
403
-
-**`--proxyServer`**
403
+
-**`--proxyServer`/ `--proxy-server`**
404
404
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