Overview
The Chrome sandbox image starts:- Xtigervnc server on display
:1for visual access - Chromium browser with remote debugging enabled on port
9222 - execd daemon on port
44772for command execution
Getting the Chrome Image
You can either build the image from source or pull a pre-built version.Build from Source
Pull Pre-built Image
Setup OpenSandbox Server
Start the OpenSandbox server locally:Usage Example
Here’s a complete example showing how to create a Chrome sandbox and access its endpoints:Accessing the Browser
VNC Access
Connect to the VNC endpoint using any VNC client:DevTools Protocol
Access the Chrome DevTools Protocol for programmatic control:Integration with MCP
You can use the Chrome sandbox with Model Context Protocol (MCP) clients for AI-driven browser automation. See the chrome-devtools-mcp project for integration details.Available Endpoints
| Port | Service | Description |
|---|---|---|
| 44772 | execd | Command execution daemon |
| 5901 | VNC | Visual access to browser |
| 9222 | DevTools | Chrome DevTools Protocol |
Use Cases
- Web Scraping: Use DevTools Protocol to extract data from websites
- Browser Testing: Automate browser interactions for testing
- Visual Debugging: Connect via VNC to see what the browser is doing
- AI Agents: Enable AI models to interact with web content through MCP