Gemini CLI browser MCP

Give Gemini CLI a browser that stays open.

Local MCP endpoint

http://127.0.0.1:47812/mcp

Start Hronaut once and leave it running. Gemini CLI can restart or switch repositories without owning the browser. The endpoint listens on loopback; it is not a hosted browser.

Choose the right browser

Gemini's browser or Hronaut?

Both are valid. The difference is who owns the browser's lifetime. Official Gemini CLI browser-agent modes ↗

Built into Gemini CLI

Gemini's browser agent

Experimental. Supports persistent, isolated, and existing session modes. A good fit when Gemini should own or attach to the browser for its run. Its lifecycle code closes browser managers on /clear and CLI exit. Official lifecycle source ↗

Separate desktop app

Hronaut

A separate visible desktop process with named workspaces and explicit pause and takeover. One browser that outlives each CLI process and stays available to Gemini CLI, Codex, Claude Code and other MCP clients.

Hronaut is a local Electron/Chromium app with a loopback endpoint. It is not a hosted browser, proxy, CAPTCHA service or multi-browser CI runner. See how task, MCP transport, and browser lifetimes differ →

Step 1 · Connect

Connect Gemini CLI.

Start Hronaut, then add it to your user settings in ~/.gemini/settings.json, so it works in every repository on this computer.

Authentication on (default)

Copy the configuration from Hronaut Home

Copy the Gemini CLI configuration from Hronaut Home. It adds Hronaut to mcpServers with the current endpoint and the authorization header a new Hronaut profile requires.

Keep the owner token out of chat, screenshots, shell history, issues and source control.

Turned authentication off?

Use this only with a profile whose Require MCP authentication is off, such as one from before Hronaut 3.5 that kept that setting. While authentication is on, Hronaut rejects a connection without the token.

Authentication off

Add Hronaut to Gemini CLI

gemini mcp add --scope user --transport http hronaut http://127.0.0.1:47812/mcp

The command combines Gemini CLI's documented HTTP transport and user scope. Official Gemini CLI v0.57.0 MCP options ↗

Step 2 · Verify

Check that it works.

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

  1. 1

    Gemini CLI sees Hronaut

    Run gemini mcp list. Hronaut should show the Streamable HTTP endpoint displayed on Hronaut Home. Inside Gemini CLI, /mcp list shows detailed status and connection diagnostics.

  2. 2

    Hronaut sees Gemini CLI

    Open Hronaut Home. Gemini CLI 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 opens Example Domain, and Gemini CLI reports its workspace ID.

Security

Protect your signed-in sessions.

Keep authentication on. A new Hronaut profile requires the owner token for MCP, so other processes running as your user cannot drive the browser. A profile from before Hronaut 3.5 keeps the setting it saved: if Require MCP authentication is off in Settings → MCP security, turn it on before you use valuable sign-ins and copy the token-aware configuration from Hronaut Home.

Treat web pages as untrusted. Websites can contain prompt injection, and a signed-in workspace carries the authority of every site in it. Keep sensitive work isolated and review surprising requests.

Take over for human-only steps. Use Hronaut's pause and interaction-lock controls before you enter passwords, security keys, payment details or other human-only information.

Keep going

Next steps.

Give every durable browser job its own named workspace. Then learn how to hand off a login safely or run several agents side by side.

Sources

Last verified against Gemini CLI v0.57.0 on August 27, 2026. Hronaut is an independent project and is not affiliated with or endorsed by Google.