launch_chrome
Launch Chrome in debug mode to automate tasks, manage extensions, and inject userscripts via the Chrome Debug MCP Server. Configure Chrome settings like user data directory, executable path, and disabled extensions for controlled debugging.
Instructions
Launch Chrome in debug mode
Input Schema
Name | Required | Description | Default |
---|---|---|---|
disableAutomationControlled | No | Disable Chrome's "Automation Controlled" mode (optional, default: false) | |
disableExtensionsExcept | No | Path to extension that should remain enabled while others are disabled (optional) | |
executablePath | No | Path to Chrome executable (optional, uses bundled Chrome if not provided) | |
loadExtension | No | Path to unpacked extension directory to load (optional) | |
url | No | URL to navigate to (optional) | |
userDataDir | No | Path to a specific user data directory (optional, uses default Chrome profile if not provided) | |
userscriptPath | No | Path to userscript file to inject (optional) |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from Chrome Debug MCP Server
Related Tools
- @robertheadley/chrome-debug-mcp
- @robertheadley/chrome-debug-mcp
- @nicholmikey/chrome-tools-MCP
- @merajmehrabi/puppeteer-mcp-server
- @nicholmikey/chrome-tools-MCP