MCP Chrome Binary

A Go-based Chrome automation service that provides WebSocket-based control over Chrome browser instances, supporting both headless and headful modes.

Features

• WebSocket-based communication
• Support for both headless and headful Chrome instances
• Session management
• URL navigation
• HTML content extraction
• Markdown conversion
• Link extraction
• Health monitoring
• Graceful shutdown handling

Prerequisites

• Go 1.21 or later
• Chrome browser installed
• Task (optional, for using taskfile commands)

Installation

1. Clone the repository:

git clone https://github.com/digged-org/mcp-chrome-bin.git
cd mcp-chrome-bin

2. Install dependencies:

go mod download

3. Install development tools (optional):

task install:tools

Configuration

The application requires the following environment variables:

• WS_URL: WebSocket server URL
• TOKEN: Authentication token
• PASSKEY: Encryption key for secure communication

Usage

Development

Run the application locally:

task run

Building

Build for all platforms:

task build:all

Build for specific platform:

task build:mac    # For macOS
task build:linux  # For Linux
task build:windows # For Windows

Testing and Linting

Run tests:

task test

Run linters:

task lint

Run security checks:

task check:security

Deployment

Create a new release:

task deploy

API Commands

The service supports the following WebSocket commands:

• open_url: Opens a new URL in Chrome
• get_outer_html: Retrieves the outer HTML of the current page
• get_markdown: Converts the current page to markdown
• get_links: Extracts all links from the current page
• health_check: Monitors application health

Health Monitoring

The service automatically sends health updates including:

• Uptime
• Memory usage
• Active sessions count
• System information

Security

• All communication is encrypted using the provided passkey
• Authentication is required via token
• Secure WebSocket connection

License

MIT License - see LICENSE file for details

Contributing

1. Fork the repository
2. Create your feature branch
3. Commit your changes
4. Push to the branch
5. Create a new Pull Request