HRONAUT
Download

Zoo Code browser MCP

Give Zoo Code a browser that survives the editor task.

Hronaut is a visible Chromium browser that runs as its own app. Zoo Code connects over Streamable HTTP, and your named workspaces, sign-ins and tabs stay available after the editor task ends.

Connect Zoo CodeDownload Hronaut

Local MCP endpoint

http://127.0.0.1:47812/mcp

Run Zoo Code and Hronaut on the same computer. A hosted or remote agent cannot reach this loopback endpoint without a separately designed secure transport.

Step 1 · Connect

Connect Zoo Code.

Start Hronaut. In the Zoo Code pane, choose MCP Servers, then Edit Global MCP. Use the first configuration only while Hronaut authentication is off.

Authentication off (default)

Minimal local configuration

{
  "mcpServers": {
    "hronaut": {
      "type": "streamable-http",
      "url": "http://127.0.0.1:47812/mcp",
      "alwaysAllow": [],
      "disabled": false
    }
  }
}

Authentication on

Read the owner token from the editor's environment

{
  "mcpServers": {
    "hronaut": {
      "type": "streamable-http",
      "url": "http://127.0.0.1:47812/mcp",
      "headers": {
        "Authorization": "Bearer ${env:HRONAUT_MCP_TOKEN}"
      },
      "alwaysAllow": [],
      "disabled": false
    }
  }
}

Set HRONAUT_MCP_TOKEN in the trusted environment that launches the editor, then restart the editor so Zoo Code can resolve it. Copy the token setup command from Hronaut Home.

Never paste the token itself into this JSON, chat, source control, screenshots or shell history.

Coming from Roo Code?

Zoo Code is the active community continuation of the discontinued Roo Code project. Verify the current package and repository before you install it. The setup above depends only on Zoo Code's standard MCP configuration and does not install a Zoo Code package.

Step 2 · Verify

Check that it works.

Use a clean workspace for this check, before Zoo Code goes near a signed-in page.

  1. 1

    Zoo Code sees Hronaut

    Under MCP Servers, confirm that hronaut is connected. Keep alwaysAllow empty at first, and add only actions you have reviewed.

  2. 2

    Hronaut sees Zoo Code

    Open Hronaut Home. The new client should appear under Connections.

  3. 3

    Run a first browser task

    Ask: “Create a Hronaut workspace named first-check, open https://example.com inside it, and tell me the page title and workspace ID. Start with clean scratch storage.”

    Expected result: a visible first-check workspace shows Example Domain. To prove the browser outlived the task, reconnect with the workspace ID and private resume key, then inspect the page again.

Security

Protect your signed-in sessions.

Turn on authentication. Any local client that can reach an unprotected Hronaut endpoint can control its agent workspaces. Enable MCP authentication before you use valuable sign-ins, and keep the owner token out of configuration files.

Take over for human-only steps. Keep Hronaut's pause and tab-lock controls within reach. Pause MCP before you enter passwords, security keys, payment details or recovery material.

Keep going

Next steps.

Give every durable Zoo Code job its own named workspace. It keeps site state apart from other workspaces and stays available to later Zoo Code tasks or another MCP client. Learn how to hand off a login safely or run several agents side by side.

Download HronautAll client setup
Sources

Hronaut is an independent project and is not affiliated with or endorsed by Zoo Code.