Cline browser MCP
Give Cline a browser that outlives the task.
Hronaut is a visible Chromium browser that runs as its own app. Cline's IDE extension or CLI connects over loopback MCP, and your named workspaces stay available after a Cline task ends or another MCP client takes over.
Local MCP endpoint
http://127.0.0.1:47812/mcp
Hronaut listens on loopback. It works with Cline clients on the same machine and is not a hosted browser for remote agents.
Choose the right browser
Cline's browser or Hronaut?
Cline already has built-in browser automation. Its browser_action tool uses Puppeteer for navigation, coordinate clicks, typing, screenshots and console capture, and its documented task lifecycle includes Automatic cleanup on task completion. Official Cline browser lifecycle source ↗
Built into Cline
One Cline task
Use browser_action when the browser is temporary task machinery and cleanup at completion is what you want.
Separate desktop app
Beyond one task or client
Use Hronaut when a named browser workspace should stay visible after a task finishes, with explicit pause and takeover, and stay available to another compatible MCP client.
The difference is lifecycle ownership, not whether Cline can automate a browser.
Step 1 · Connect
Connect Cline.
Start Hronaut first. Cline's IDE extension and CLI support local stdio servers plus remote Streamable HTTP and legacy SSE servers. In Cline's MCP panel, add a remote server, choose Streamable HTTP and enter the endpoint, or add the same definition with cline mcp. Official Cline MCP setup ↗
Authentication on (default)
Copy the configuration from Hronaut Home
Copy the Cline configuration from Hronaut Home. It adds the Authorization header a new Hronaut profile requires; keep its explicit streamableHttp type. Do not commit the owner token or paste it into chat.
Set the type explicitly: Cline treats an untyped URL as legacy SSE for backward compatibility. Keep autoApprove empty while you check the connection.
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
Streamable HTTP definition
{
"mcpServers": {
"hronaut": {
"type": "streamableHttp",
"url": "http://127.0.0.1:47812/mcp",
"disabled": false,
"autoApprove": []
}
}
}The Cline CLI wizard accepts the same name, transport and URL.
Step 2 · Verify
Check that it works.
Use a clean workspace for this check, before Cline goes near a signed-in page.
- 1
Cline sees Hronaut
Open Cline's MCP Servers panel, or run
cline config mcp --json, and confirm that hronaut is enabled. The interactive manager iscline mcp. Leave MCP auto-approval off until the server and tool list match what you expect. - 2
Hronaut sees Cline
Open Hronaut Home. Cline should appear under Connections.
- 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 separate, visible
first-checkworkspace opens Example Domain, and Cline 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.
Treat web pages as untrusted. Websites can contain prompt injection, so review surprising MCP calls.
Take over for human-only steps. Pause MCP 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
- Cline MCP overview — Streamable HTTP, legacy SSE, the MCP panel and CLI.
- Cline browser lifecycle source —
browser_actionand cleanup on task completion. - Hronaut source — loopback transport, authentication, workspaces and human controls.
Last verified against Cline's official MCP and browser lifecycle documentation on August 27, 2026. Hronaut is an independent project and is not affiliated with or endorsed by Cline.