Skip to content

Chrome DevTools for coding agents

docs: clarify custom browser launch and connection options (#3386)

a57685497e10c08d3017
diff --git a/README.md b/README.md
index 970f869d..2dca1a05 100644
--- a/README.md
+++ b/README.md
@@ -177,7 +177,7 @@ For basic browser tasks only, the `--slim` flag exposes a reduced set of tools.
## Advanced Usage
-For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Chrome instance instead of starting a new one, or debugging on Android, see our [Advanced Usage Guide][advanced-usage-guide].
+For advanced features such as handling concurrent sessions, persistent user data directories, using a custom or non-standard browser path (`--executablePath`), connecting to a running Chrome instance instead of starting a new one, or debugging on Android, see our [Advanced Usage Guide][advanced-usage-guide].
## Integrating as a browser subagent
diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md
index 8cb5720b..e92eea14 100644
--- a/docs/advanced-usage.md
+++ b/docs/advanced-usage.md
@@ -40,6 +40,29 @@ runs with the same channel. Only one browser can use it at a time. Set the `isol
option to `true` to use a temporary user data directory instead which will be cleared
automatically after the browser is closed.
+## Custom browser executable
+
+By default, `chrome-devtools-mcp` launches Chrome installed in the standard
+location for the selected channel. To launch a Chrome-based browser installed
+in a custom or non-standard location, pass its executable path with
+`--executablePath` (or `-e`):
+
+```json
+{
+ "mcpServers": {
+ "chrome-devtools": {
+ "command": "npx",
+ "args": ["chrome-devtools-mcp@latest", "--executablePath=/path/to/chrome"]
+ }
+ }
+}
+```
+
+`--executablePath` only applies when the MCP server launches the browser. It
+cannot be combined with `--channel`, `--autoConnect`, `--browserUrl` or
+`--wsEndpoint`. To use a browser that is already running, see
+[Connecting to a running Chrome instance](#connecting-to-a-running-chrome-instance).
+
## Connecting to a running Chrome instance
By default, the Chrome DevTools MCP server will start a new Chrome instance with a dedicated profile. This might not be ideal in all situations: