JetBrains Junie browser MCP
Give local Junie sessions a browser that survives the task.
Hronaut is a visible Chromium browser that runs as its own app. Local Junie CLI and IDE sessions connect over loopback MCP, and your named workspaces stay available after a task ends or another MCP client takes over.
Local MCP endpoint
http://127.0.0.1:47812/mcp
The loopback endpoint exists only on the computer running Hronaut. It works with Junie on that same computer; it is not a hosted remote-browser service.
Step 1 · Connect
Connect Junie.
Start Hronaut, then add Hronaut to ~/.junie/mcp/mcp.json. Junie CLI uses the same MCP JSON configuration as Junie in JetBrains IDEs, so one user-level entry covers both. A project-level .junie/mcp/mcp.json can be shared with a repository, but should not contain secrets. Official Junie MCP configuration ↗
Authentication on (default)
Use a private literal header or Junie's assistant
Find the current protected setup on Hronaut Home. Then either use Junie's /mcp Installation Assistant or put the literal bearer value in the user-level file's documented headers object. Keep it out of project configuration, chat, screenshots and source control.
Junie's public MCP guide does not document file or environment interpolation for static header values, so this guide does not invent token placeholders.
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
~/.junie/mcp/mcp.json
{
"mcpServers": {
"hronaut": {
"url": "http://127.0.0.1:47812/mcp"
}
}
}This follows Junie's documented remote-server format and contains no bearer token.
Step 2 · Verify
Check that it works.
Use a clean workspace for this check, before Junie goes near a signed-in page.
- 1
Junie sees Hronaut
Run
/mcpin Junie and confirm that hronaut reports Active. In ACP clients,/mcpis a read-only listing; edit the JSON file or use a supported Junie management surface to change configuration. Review the server and tool list before you allow calls automatically. - 2
Hronaut sees Junie
Open Hronaut Home. Junie 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 Junie 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 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
- Junie MCP configuration — the shared CLI and IDE file, user and project scopes, remote URL and header fields, and
/mcpstatus. - Junie IDE integration — how the same Junie CLI session appears in supported JetBrains IDEs.
- Junie CLI quickstart — installing and starting Junie CLI.
Last verified against JetBrains' official Junie documentation on August 28, 2026. Hronaut is an independent project and is not affiliated with or endorsed by JetBrains or Junie.