hronaut
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hronautopen a new tab and navigate to https://news.ycombinator.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hronaut
Hronaut is a visible, persistent Electron browser that exposes its live tabs to AI clients through MCP. It keeps the browser open independently of any individual AI session, so humans and agents can share the same local browsing context.
Website · Downloads · Issues · Detailed reference
Highlights
Persistent tabs, cookies, storage, sessions, workspaces, split views, and window state.
Local Streamable HTTP MCP endpoint with browser navigation, interaction, inspection, diagnostics, downloads, storage, and accessibility tools.
Multi-agent workspaces with stable UUIDv7 identities and isolated browser profiles.
Human-interaction locks, instant MCP pause, explicit permissions, and optional bearer-token authentication.
Built-in history, bookmarks, downloads, password vault, site controls, responsive preview, visual comparison, and Chromium diagnostics.
Automatic update checks against public GitHub releases; downloads and installation always require user action.
English, Ukrainian, Russian, German, French, Spanish, and Polish interface languages.
Related MCP server: Playwright MCP Server
Install
Download the latest package for Windows, macOS, or Linux from GitHub Releases.
The initial release artifacts are not platform code-signed or Apple-notarized, so Windows SmartScreen or macOS Gatekeeper may show a warning. Verify downloads with the published hashes.txt file and GitHub artifact attestations.
Run from source
Requirements: Node.js 22 or newer and a graphical Linux, macOS, or Windows session.
npm install
npm run devBuild and run the desktop application:
npm run build
npm startDevelopment uses a separate persistent hronaut-dev profile. Installed builds use the normal Hronaut profile.
Connect an MCP client
Start Hronaut, then configure a Streamable HTTP client with the local endpoint:
{
"mcpServers": {
"hronaut": {
"url": "http://127.0.0.1:47812/mcp"
}
}
}Hronaut Home contains current setup instructions for Codex, Claude Code, Cursor, VS Code/GitHub Copilot, and generic MCP clients.
The server listens only on loopback. Authentication is optional for a new profile and can be enabled under Settings → MCP security.
Development checks
npm run lint
npm test
npm run typecheck
npm run build
npm run test:integration:headlessRelease packaging and publishing are centralized in .github/workflows/release.yml. Every local package command uses --publish never.
License
Hronaut is source-available under the PolyForm Noncommercial License 1.0.0. Uses not permitted by that license require an active commercial subscription license.
Outside contributions are welcome under the terms in CONTRIBUTING.md. Security reports should follow SECURITY.md.
For billing and licensing support, contact support@hronaut.dev.
Documentation
The detailed reference covers browser behavior, privacy and security boundaries, every MCP tool group, testing, packaging, and release operations.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceLets AI coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.11Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables browser automation through the MCP protocol, allowing AI agents to control a real browser using accessibility snapshots and natural language commands.
- AlicenseNot gradedqualityBmaintenanceLets coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.2,211,104Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hronaut/hronaut'
If you have feedback or need assistance with the MCP directory API, please join our Discord server