Chrome DevTools MCP

Start Chrome with remote debugging enabled and optionally establish connection. Launches Chrome browser with DevTools Protocol debugging enabled on the specified port. Supports both headless and windowed modes, with automatic executable detection across platforms. Can optionally connect to the started instance and navigate to a specific URL in a single operation. The function handles existing Chrome instances gracefully, detecting if Chrome is already running on the target port and optionally connecting to it rather than attempting to start a new instance. Args: port: TCP port for Chrome remote debugging server (default: 9222). Must be available or already in use by Chrome. url: Initial URL to navigate to after starting Chrome. If provided, Chrome will load this page on startup. headless: Whether to run Chrome in headless mode without GUI. Useful for automated testing and server environments. chrome_path: Custom path to Chrome executable. If not provided, uses automatic detection based on platform. auto_connect: Whether to automatically connect to Chrome and enable debugging domains after startup. Returns: Comprehensive status dictionary containing: - success: Boolean indicating operation success - message: Human-readable status description - data: Detailed information including: - port: Port Chrome is running on - pid: Process ID of Chrome instance (if started) - connected: Whether connection was established - navigated: Whether URL navigation succeeded - alreadyRunning: Whether Chrome was already running Raises: The function handles exceptions internally and returns error responses rather than raising exceptions. Check the 'success' field in the response. Note: Uses a temporary user data directory to avoid conflicts with existing Chrome profiles. The directory location is platform-specific.

Start Chrome with debugging, connect, and navigate to URL in one step. Convenience function that combines browser startup, connection establishment, and navigation into a single operation. Equivalent to calling start_chrome with auto_connect=True and a URL parameter. This function is ideal for quick browser automation tasks where you need to get Chrome running and navigate to a specific page without manual connection management. Args: url: Target URL to navigate to after Chrome startup. Must be a valid URL that Chrome can load. port: TCP port for Chrome remote debugging server (default: 9222). Must be available or already in use by Chrome. headless: Whether to run Chrome in headless mode without GUI. Particularly useful for automated testing scenarios. chrome_path: Custom path to Chrome executable. If not provided, uses automatic platform-specific detection. Returns: Combined status dictionary containing startup, connection, and navigation results. Includes all fields from start_chrome plus navigation status. Note: This is a convenience wrapper around start_chrome with auto_connect=True. For more granular control over the startup process, use start_chrome directly.

Connect to an existing Chrome instance with remote debugging enabled. Establishes a connection to a Chrome browser that's already running with remote debugging enabled on the specified port. Enables necessary DevTools Protocol domains and retrieves browser information. This function is useful when Chrome is already running (perhaps started manually or by another process) and you want to control it programmatically. It verifies the browser is accessible before attempting connection. Args: port: TCP port where Chrome remote debugging is listening (default: 9222). Chrome must be started with --remote-debugging-port=PORT for this to work. Returns: Connection status dictionary containing: - success: Boolean indicating connection success - message: Human-readable status description - data: Connection details including: - connected: Boolean connection status - port: Port Chrome is running on - targetInfo: Browser version and capability information Note: If Chrome is not running on the specified port, the function returns an error response with suggestions for starting Chrome with the correct debugging options.

Navigate the connected browser to a specific URL. Instructs the currently connected Chrome instance to navigate to the specified URL. The function waits briefly for the navigation to begin before returning. Requires an active connection to Chrome established via connect_to_browser or start_chrome with auto_connect. Args: url: Target URL to navigate to. Must be a valid URL that Chrome can load, including HTTP/HTTPS websites, local file paths, or data URIs. Returns: Navigation status dictionary containing: - success: Boolean indicating navigation success - message: Human-readable status description - data: Navigation details including: - url: The URL navigated to - navigated: Boolean navigation status Note: The function returns immediately after initiating navigation and doesn't wait for the page to fully load. Use additional tools to monitor page load completion if needed.

Disconnect from the current browser session. Cleanly terminates the connection to the Chrome browser instance while leaving the browser running. This is useful for releasing resources or preparing to connect to a different browser instance. The browser will continue running after disconnection, but will no longer be controllable through this client until a new connection is established. Returns: Disconnection status dictionary containing: - success: Boolean indicating disconnection success - message: Human-readable status description - data: Disconnection details including: - connected: Boolean status (should be False after disconnect) Note: This function only disconnects the client from Chrome; it doesn't close or terminate the browser process itself.