Codex
User-level configuration
Hronaut adds the server to ~/.codex/config.toml.
codex mcp add hronaut --url http://127.0.0.1:47812/mcp
MCP setup guide
Start Hronaut once, connect through its loopback Streamable HTTP endpoint, and keep the same visible browser across coding-agent tasks.
Default endpoint
http://127.0.0.1:47812/mcpHronaut listens only on loopback. If you change the port or enable authentication, copy the current client-specific snippet from Hronaut Home; it always reflects the active settings.
Start here
Download the package for Windows, macOS, or Linux. Initial builds are unsigned, so review the warning and verify the published hashes or artifact attestations.
Confirm that the MCP server is online and copy the setup for your client. New profiles default to port 47812.
Use the matching command or JSON below, then refresh or restart the coding agent so it loads the new MCP server.
Hronaut Home shows active and recently seen clients. Ask the agent to create a named workspace before it opens pages.
Copy tested setup
These examples match a new profile with authentication disabled. If authentication is enabled, use the exact token-aware snippet shown by Hronaut Home instead of pasting a token into chat or source control.
Codex
Hronaut adds the server to ~/.codex/config.toml.
codex mcp add hronaut --url http://127.0.0.1:47812/mcp
Claude Code
The user scope makes Hronaut available across projects.
claude mcp add --transport http --scope user hronaut http://127.0.0.1:47812/mcp
Cursor
~/.cursor/mcp.jsonSave globally, or use the same object in a project's .cursor/mcp.json.
{
"mcpServers": {
"hronaut": {
"url": "http://127.0.0.1:47812/mcp"
}
}
}
VS Code / GitHub Copilot
.vscode/mcp.jsonSave in the workspace, or use MCP: Open User Configuration for global access.
{
"servers": {
"hronaut": {
"type": "http",
"url": "http://127.0.0.1:47812/mcp"
}
}
}
Generic MCP client
Use the standard transport and point the client directly at Hronaut.
{
"name": "hronaut",
"transport": "streamable-http",
"url": "http://127.0.0.1:47812/mcp"
}
Security boundary
Authentication is off for a new profile so local clients can connect immediately. In that mode, any process running as you can control the Hronaut browser profile. For profiles containing sensitive signed-in sessions, open Settings → MCP security, enable Require MCP authentication, and copy the regenerated client setup from Hronaut Home.
The token is stored in an owner-only file and is never displayed by Hronaut Home. Do not paste it into issues, screenshots, source control, or community posts.
First task
After the client appears under Connections, try: “Create a Hronaut workspace named dashboard-debug, open the application, and keep all work for this task inside that workspace.”