From 9f81778b16db07f7c1ac48be74da386731aa9002 Mon Sep 17 00:00:00 2001 From: Sebastian Benz Date: Wed, 26 Nov 2025 19:31:05 +0100 Subject: [PATCH 1/2] docs: clarify browser-url parameter in README Fixes #609 --- README.md | 2 +- src/cli.ts | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5864b073..6f69c71e 100644 --- a/README.md +++ b/README.md @@ -322,7 +322,7 @@ The Chrome DevTools MCP server supports the following configuration option: - **`--browserUrl`, `-u`** - Connect to a running Chrome instance using port forwarding. For more details see: https://developer.chrome.com/docs/devtools/remote-debugging/local-server. + Connect to a running Chrome instance using port forwarding. The value of this option should be the URL of the running Chrome instance together with the configured debugging port. `http://127.0.0.1:9222` is a common default. For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#connecting-to-a-running-chrome-instance. - **Type:** string - **`--wsEndpoint`, `-w`** diff --git a/src/cli.ts b/src/cli.ts index 15808537..0634ac1d 100644 --- a/src/cli.ts +++ b/src/cli.ts @@ -11,7 +11,7 @@ export const cliOptions = { browserUrl: { type: 'string', description: - 'Connect to a running Chrome instance using port forwarding. For more details see: https://developer.chrome.com/docs/devtools/remote-debugging/local-server.', + 'Connect to a running Chrome instance using port forwarding. The value of this option should be the URL of the running Chrome instance together with the configured debugging port. `http://127.0.0.1:9222` is a common default. For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#connecting-to-a-running-chrome-instance.', alias: 'u', conflicts: 'wsEndpoint', coerce: (url: string | undefined) => { From fc4cb50e6437d65af0d851f44eebe0ca97082c60 Mon Sep 17 00:00:00 2001 From: Sebastian Benz Date: Thu, 27 Nov 2025 10:44:34 +0100 Subject: [PATCH 2/2] Update README.md Co-authored-by: Paul Irish --- README.md | 2 +- src/cli.ts | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6f69c71e..63e93d4d 100644 --- a/README.md +++ b/README.md @@ -322,7 +322,7 @@ The Chrome DevTools MCP server supports the following configuration option: - **`--browserUrl`, `-u`** - Connect to a running Chrome instance using port forwarding. The value of this option should be the URL of the running Chrome instance together with the configured debugging port. `http://127.0.0.1:9222` is a common default. For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#connecting-to-a-running-chrome-instance. + 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. - **Type:** string - **`--wsEndpoint`, `-w`** diff --git a/src/cli.ts b/src/cli.ts index 0634ac1d..4a5d89ce 100644 --- a/src/cli.ts +++ b/src/cli.ts @@ -11,7 +11,7 @@ export const cliOptions = { browserUrl: { type: 'string', description: - 'Connect to a running Chrome instance using port forwarding. The value of this option should be the URL of the running Chrome instance together with the configured debugging port. `http://127.0.0.1:9222` is a common default. For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#connecting-to-a-running-chrome-instance.', + '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.', alias: 'u', conflicts: 'wsEndpoint', coerce: (url: string | undefined) => {