HRONAUT
Download

Kiro browser MCP

Give local Kiro sessions a browser that stays visible.

Kiro keeps agent configuration and work moving across its surfaces. Hronaut adds a different lifetime: a separate visible Chromium application whose named workspaces, tabs, sign-ins, and storage stay under local desktop and human control.

Add to KiroManual setupDownload Hronaut

Hronaut is an independent project and is not affiliated with or endorsed by Kiro or Amazon Web Services.

Local MCP endpoint

http://127.0.0.1:47812/mcp

Use this loopback endpoint from the Kiro IDE or CLI running on the same computer. Kiro Web and Mobile do not support remote HTTP MCP, and a cloud sandbox cannot reach Hronaut on your desktop.

Match the tool to the job

Agent continuity and browser continuity are different.

Kiro's unified agent harness carries configuration across IDE, CLI, Web, and Mobile, and its built-in tools can search and fetch web content. Use those surfaces for code and document work. Use Hronaut from a local Kiro session when the task needs an interactive browser that remains visibly available outside the agent's own lifecycle. Official Kiro architecture ↗ Official MCP surface matrix ↗

Kiro built-ins

Code and web content

Use Kiro's native tools when search, fetched content, repository changes, or a cloud-backed agent session is sufficient.

Kiro MCP

Local IDE or CLI tools

Kiro supports localhost HTTP MCP from its local IDE and CLI. Save Hronaut in user configuration when it should be available across local projects.

Separate browser lifetime

Durable named workspaces

Use Hronaut when browser state should remain in a separately managed desktop application across local agent sessions and reconnects.

Human handoff

Pause and take over

Watch the browser, pause MCP before a sensitive step, interact manually, then let Kiro continue in the same workspace.

One-click or user-level setup

Connect Kiro IDE or CLI to Hronaut.

Start Hronaut, then use Add to Kiro and review Kiro's confirmation before accepting it. For an explicit user-level installation, run Kiro: Open user MCP config (JSON) from the Command Palette and add the same server to ~/.kiro/settings/mcp.json. Official install-link format ↗ Official configuration reference ↗

Authentication disabled

User mcp.json

{
  "mcpServers": {
    "hronaut": {
      "url": "http://127.0.0.1:47812/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Keep autoApprove empty while verifying the tools and connection. Kiro accepts plain HTTP specifically for localhost endpoints. The one-click link contains no secret and is complete only while Hronaut authentication is disabled.

Authentication enabled

Use the owner-only token file

Enable Require MCP authentication in Hronaut. Its Generic MCP client card identifies the owner-only token file and required Authorization header. Add that header to Kiro's headers object in user configuration; do not commit the token to .kiro/settings/mcp.json, an agent file, screenshots, issues, or chat.

Verify before using a login

Prove the local connection in an isolated workspace.

  1. 1

    Confirm the server

    Open the MCP servers tab in the Kiro panel and confirm hronaut is connected. For diagnostics, open the Output tab and select Kiro - MCP Logs.

  2. 2

    Keep approval on

    Leave autoApprove empty until the Hronaut tool list and requested operations match what you expect.

  3. 3

    Create a clean first workspace

    Ask: “Create a Hronaut workspace named first-check, open https://example.com inside it, and tell me the page title and workspace ID. Do not use my Default workspace.”

  4. 4

    Confirm the observable result

    A separate visible first-check workspace opens Example Domain, and Kiro reports its stable workspace ID.

Security boundary

Keep browser authority local and deliberate.

A new Hronaut profile starts without MCP authentication for simple local setup. Before using valuable signed-in sessions, enable Require MCP authentication. Websites can contain prompt injection, and a persistent workspace carries the authority of every site signed in inside it. Review surprising MCP calls and pause MCP before entering passwords, security keys, payment details, or other human-only information.

Choose deliberately

Use Kiro's surfaces for the agent. Use Hronaut when the local browser needs its own lifetime.

Hronaut does not make Kiro Web a remote control for your desktop. It gives locally running Kiro IDE and CLI sessions a separately visible browser, durable named profiles, and explicit pause and takeover controls.

Last verified against Kiro's official MCP, configuration, install-link, and agent-architecture documentation on August 27, 2026.

Add to KiroChoose a desktop packageSafe login handoffInspect the source