launchChrome
Launch a Chrome browser instance with debugging support, configurable with headless mode, viewport dimensions, and extra Chrome flags for automation.
Instructions
Launch Chrome with debugging
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "launchChrome"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | URL to open (default: blank page) | |
| port | No | The debugging port (optional, defaults to this session's reserved port). Use this to launch multiple Chrome instances on different ports. | |
| width | No | Viewport width in pixels (optional). If set, the browser viewport will be resized after launch. | |
| height | No | Viewport height in pixels (optional). If set, the browser viewport will be resized after launch. | |
| headless | No | Launch in headless mode (no visible window, prevents focus stealing). Default: false | |
| reference | No | Connection reference name (3 descriptive words). If not provided, defaults to "unnamed-connection-default". Use this to identify the connection when calling other tools. | |
| chromeArgs | No | Extra Chrome command-line flags to pass through at launch, e.g. ["--use-fake-device-for-media-stream", "--use-fake-ui-for-media-stream"]. Merged after the managed defaults. The CDP_TOOLS_EXTRA_CHROME_ARGS env var (space-separated) is also always merged. Only applies when this call actually launches Chrome (ignored when an existing instance on the port is reused). | |
| autoConnect | No | Automatically connect debugger after launch | |
| forceNewInstance | No | Always spawn a fresh Chrome process on a new port instead of reusing/tabbing into an existing instance |