Skip to content

Chrome DevTools for coding agents

docs: clarify browser-url parameter in README (#613)

Sebastian Benz05cf8cb8a6c6
diff --git a/README.md b/README.md
index 5864b073..63e93d4d 100644
--- a/README.md
+++ b/README.md
@@ -322,7 +322,7 @@ The Chrome DevTools MCP server supports the following configuration option:
<!-- BEGIN AUTO GENERATED OPTIONS -->
- **`--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, 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 15808537..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. For more details see: https://developer.chrome.com/docs/devtools/remote-debugging/local-server.',
+ '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) => {