C

Chrome Tools

Integrates with Chrome's DevTools Protocol to enable remote control of browser tabs, including JavaS...

87 views
0 installs
Updated Sep 9, 2025
Not audited
Integrates with Chrome's DevTools Protocol to enable remote control of browser tabs, including JavaScript execution, screenshot capture, and network traffic monitoring.
  1. Launch Chrome with Remote Debugging Enabled
    Open your operating system’s terminal or command prompt and start Chrome with the remote debugging port (9222):

    • Windows:
      "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222
      
    • Mac:
      /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
      
    • Linux:
      google-chrome --remote-debugging-port=9222
      
  2. Copy Debug URL Value
    By default, the debug interface is available at:

    http://localhost:9222
    
  3. Determine Connection Type

    • If running everything on one machine (or you are using Docker with port 9222 forwarded): use direct or docker as the connection type.
    • If your browser runs in a different OS (for example, via WSL) and you are tunneling the port, use ssh-tunnel.
  4. Set Values in the FastMCP Connection Interface
    In the FastMCP integration settings (using the "Install Now" button), enter the following values:

    • CHROME_DEBUG_URL: Set this to your debugging URL (usually http://localhost:9222).
    • CHROME_CONNECTION_TYPE: Set this to one of: direct, ssh-tunnel, or docker.
    • (Optional) CHROME_ERROR_HELP: You may add a custom error message to display if a connection fails (for example, suggest checking the debugging port or tunneling status).

Example values:

  • CHROME_DEBUG_URL: http://localhost:9222
  • CHROME_CONNECTION_TYPE: direct

For WSL/SSH Tunnel:

  • Launch Chrome on Windows with remote debugging
  • Run the SSH tunnel in your WSL shell:
    ssh -N -L 9222:localhost:9222 windowsuser@host
    
  • Set CHROME_CONNECTION_TYPE to ssh-tunnel
  • (Optionally) set CHROME_ERROR_HELP to:
    Make sure the SSH tunnel is running: ssh -N -L 9222:localhost:9222 windowsuser@host
    

Summary:
You do not need an API key or special token for this setup. Once Chrome is running with remote debugging, all you need to do is copy the correct debug URL and connection type into the FastMCP interface for successful integration.

Quick Start

View on GitHub

More for Browser Automation

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.