BO
toolBrowserOS
Lets agents operate a local-first Chromium browser with existing sessions through more than 50 built-in MCP browser tools.
What it provides
Connect an HTTPS browser-service API. The bot receives an isolated client; browser workers and sessions stay on the external server.
Connection requirements
A BrowserClaw MCP endpoint exposed through authenticated HTTPS
- Protocol
- Streamable HTTP MCP
- Endpoint
https://browserclaw.example.com/mcp- Authentication
- Choose the mode required by your service
Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.