HRONAUT
Download

Cursor browser MCP

Give Cursor a browser it can share across agents.

Hronaut runs a separate visible Chromium application. Cursor and Cursor CLI connect over loopback MCP while named browser workspaces remain available when you change repositories, restart one client, or continue through another compatible MCP client.

Connect CursorDownload HronautCompare browser tools

Hronaut is an independent project and is not affiliated with or endorsed by Cursor or Anysphere.

Local MCP endpoint

http://127.0.0.1:47812/mcp

Hronaut listens on loopback. It works with local Cursor clients running on the same machine and does not provide a remote browser for Cursor Cloud Agents.

Use Cursor's native option when it fits

Cursor already has a strong native Browser.

Cursor's Browser is visible in a separate window or inline pane, needs no external tool installation, and can inspect screenshots, console output, and network traffic. Browser state persists between Agent sessions, including cookies, local storage, session storage, and IndexedDB, with browser context isolated per workspace. For Cursor-only development and testing, start there. Official Cursor Browser documentation ↗

Native Browser

Cursor-owned development loop

Use Cursor's Browser when the browser belongs to one Cursor workspace and the goal is to build, inspect, and verify that project.

Native persistence

Workspace-isolated state

Cursor already preserves browser state across Agent sessions and isolates it per workspace. Hronaut does not claim that persistence or isolation is unique.

Separate ownership

Client-independent workspaces

Use Hronaut when a named browser workspace should be owned by a separate desktop app and remain available across Cursor, Cursor CLI, Codex, Claude Code, or another compatible client.

Human handoff

Pause and take over

Watch Hronaut, pause MCP before a sensitive step, interact manually, then resume an agent in the same browser workspace.

One-click or manual setup

Connect Cursor to the local Hronaut endpoint.

Start Hronaut first. The one-click link contains only the server name and default loopback URL shown below; Cursor displays a confirmation before installing it. Use manual setup when you want to inspect the file yourself.

Manual global setup

~/.cursor/mcp.json

{
  "mcpServers": {
    "hronaut": {
      "url": "http://127.0.0.1:47812/mcp"
    }
  }
}

Global configuration is personal and available across projects. Project-specific .cursor/mcp.json takes precedence, but do not commit a profile token. Save the file and restart Cursor. Official Cursor MCP setup ↗

Authentication enabled

Copy from Hronaut Home

Enable Require MCP authentication, then copy the generated Cursor configuration from Hronaut Home. It includes the current endpoint and authorization header. Do not put the owner token in a deeplink, project file, chat, screenshot, issue, or source control.

Verify before using a login

Prove the connection in an isolated Hronaut workspace.

  1. 1

    Confirm the MCP server

    In Cursor, open Customize → MCPs and confirm that hronaut is enabled. Cursor CLI uses the same configuration; run agent mcp list, or /mcp list in interactive mode, to inspect its status. Official Cursor CLI MCP commands ↗

  2. 2

    Review the available tools

    Keep only the MCP tools relevant to the task enabled, and leave tool approval on while verifying the connection.

  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 Cursor reports its stable workspace ID.

Security boundary

Keep a persistent browser's authority explicit.

A new Hronaut profile starts without MCP authentication for simple local setup. In that mode, another process running as your operating-system user could connect. Before using valuable signed-in sessions, enable Require MCP authentication and copy the exact token-aware Cursor configuration from Hronaut Home.

Websites can contain prompt injection, and a persistent authenticated workspace carries the authority of every site signed in inside it. Review surprising tool requests, keep unrelated identities in separate workspaces, and pause MCP before entering passwords, security keys, payment details, or other human-only information.

Choose deliberately

Use Cursor's Browser for a Cursor workspace. Use Hronaut for a browser workspace shared across clients.

Both options are visible and persistent. The difference is ownership: Cursor's native Browser belongs to Cursor's workspace model; Hronaut belongs to a separate local desktop application with named workspaces and explicit human controls.

Last verified against official Cursor Browser, MCP, install-link, and CLI documentation on August 27, 2026.

Choose a desktop packageAll client setupSafe login handoffInspect the source