Connect your agent.

OpenCode

~/.config/opencode/opencode.json

Use the global file to make Hronaut available across projects, or put the same configuration in opencode.json at one project root. Add Hronaut as a remote Streamable HTTP server and disable OAuth discovery because Hronaut uses either no authentication or its own optional bearer header.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hronaut": {
      "type": "remote",
      "url": "http://127.0.0.1:47812/mcp",
      "enabled": true,
      "oauth": false
    }
  }
}

This example follows the official stable OpenCode MCP guide ↗. OpenCode V2: place the same hronaut object under mcp.servers and omit enabled; V2 connects unless disabled is true. See the official V2 MCP guide ↗.

Start Hronaut, then run opencode mcp list to verify the connection. If authentication is enabled, copy the OpenCode configuration from Hronaut Home; it uses OpenCode's {file:...} substitution to read the owner-only token file without storing the token in this JSON. Run opencode mcp debug hronaut for connection or authentication diagnostics.

Open the focused OpenCode browser MCP walkthrough →

Kilo Code

~/.config/kilo/kilo.jsonc

Add Hronaut under Kilo Code's top-level mcp key. This global file is shared by local Kilo Code IDE, CLI, and JetBrains clients.

{
  "$schema": "https://app.kilo.ai/config.json",
  "mcp": {
    "hronaut": {
      "type": "remote",
      "url": "http://127.0.0.1:47812/mcp",
      "enabled": true,
      "oauth": false
    }
  }
}

Start Hronaut, then run kilo mcp list. This loopback setup works only when Kilo Code and Hronaut run on the same machine; current Kilo Cloud Agent MCP support is documented as coming. Official Kilo Code MCP guide ↗

Open the focused Kilo Code browser MCP walkthrough →

JetBrains Junie

~/.junie/mcp/mcp.json

Junie CLI and Junie in JetBrains IDEs use the same MCP JSON configuration. Use the user-level file to make Hronaut available across projects.

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

Start Hronaut, then run /mcp in Junie and confirm hronaut is Active. This loopback setup works only when Junie and Hronaut run on the same computer. Official Junie MCP guide ↗

Open the focused JetBrains Junie browser MCP walkthrough →

Devin Local

~/.config/devin/mcp_config.json

Devin Local is the default agent for new Devin Desktop tabs. Add Hronaut at user scope so the same local browser is available across projects.

devin mcp add -s user hronaut http://127.0.0.1:47812/mcp

Start Hronaut, then run devin mcp list and devin mcp get hronaut. Cloud Devin sessions cannot reach a loopback service on your computer. Existing legacy Cascade users need its Windsurf-era file and serverUrl field. Official Devin MCP guide ↗

Open the focused Devin Local browser MCP walkthrough →

Zed

User-level context_servers

Add Hronaut as a custom remote server for Zed Agent and ACP-forwarded external agents. Include the documented Authorization field so Zed does not start an OAuth flow that Hronaut does not implement.

{
  "context_servers": {
    "hronaut": {
      "url": "http://127.0.0.1:47812/mcp",
      "headers": {
        "Authorization": "Hronaut local-no-auth"
      }
    }
  }
}

The marker is not a credential and is only for a Hronaut profile with authentication disabled. For a protected profile, put the actual bearer token in private local user settings; Zed does not document secret interpolation for this field. Official Zed MCP guide ↗

Open the focused Zed browser MCP walkthrough →

Grok Build

~/.grok/config.toml

Add Hronaut to xAI's local Grok Build CLI as a user-scoped native HTTP MCP server.

grok mcp add --transport http hronaut http://127.0.0.1:47812/mcp

Start Hronaut, then run grok mcp doctor hronaut. This loopback setup is for Grok Build running on the same computer; hosted grok.com and @grok cannot reach it. Official Grok Build MCP guide ↗

Open the focused Grok Build browser MCP walkthrough →

Qwen Code

~/.qwen/settings.json

Add Hronaut to the local Qwen Code CLI as a user-scoped native Streamable HTTP MCP server.

qwen mcp add --scope user --transport http hronaut http://127.0.0.1:47812/mcp

Start Hronaut, run qwen mcp list, then use /mcp inside Qwen Code. This loopback setup is for a local Qwen Code process; Qwen Chat and remote sessions cannot reach it. Official Qwen Code MCP guide ↗

Open the focused Qwen Code browser MCP walkthrough →

Goose

~/.config/goose/config.yaml

Add Hronaut to local Goose Desktop and CLI sessions as a persistent Streamable HTTP extension.

extensions:
  hronaut:
    type: streamable_http
    name: hronaut
    enabled: true
    uri: "http://127.0.0.1:47812/mcp"
    headers: {}
    env_keys: []
    envs: {}
    timeout: 300

Start Hronaut, then open Goose Extensions to confirm the server. This configuration contains no credential and applies while Hronaut authentication is disabled. For a protected profile, reference HRONAUT_MCP_TOKEN through env_keys and Goose's secret store; never paste the owner token into config.yaml. Official Goose configuration reference ↗

Open the focused Goose browser MCP walkthrough →

Zoo Code

Global MCP configuration

Open Zoo Code → MCP Servers → Edit Global MCP, then add Hronaut as a Streamable HTTP server. Keep the approval list empty until you have reviewed the available browser tools.

{
  "mcpServers": {
    "hronaut": {
      "type": "streamable-http",
      "url": "http://127.0.0.1:47812/mcp",
      "alwaysAllow": [],
      "disabled": false
    }
  }
}

Start Hronaut and confirm hronaut is connected in Zoo Code's MCP Servers view. For protected profiles, use the environment-backed header shown by Hronaut Home. Official Zoo Code MCP guide ↗

Open the focused Zoo Code browser MCP walkthrough →

Mistral Vibe

~/.vibe/config.toml

Vibe CLI and the local VS Code extension share MCP configuration. Use explicit static authentication so Vibe does not start an OAuth flow that Hronaut does not implement.

[[mcp_servers]]
name = "hronaut"
transport = "streamable-http"
url = "http://127.0.0.1:47812/mcp"

[mcp_servers.auth]
type = "static"
headers = { "Authorization" = "Hronaut local-no-auth" }

The marker is not a credential and is only for a Hronaut profile with authentication disabled. Protected profiles can use Vibe's environment-backed API-key fields. Vibe Code Web cannot reach a loopback service on your desktop. Official Vibe MCP guide ↗

Open the focused Mistral Vibe browser MCP walkthrough →

Warp

~/.warp/.mcp.json

Warp's local Agent supports URL-based Streamable HTTP servers. A user-level definition is available across repositories and auto-spawns without trusting a project-scoped server file.

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

Open Settings → Agents → MCP servers to inspect running state, tools, and View Logs. This loopback setup is for a local Warp Agent; a Warp-hosted cloud agent cannot reach a service on your desktop. Official Warp MCP guide ↗

Open the focused Warp browser MCP walkthrough →

Windsurf

~/.codeium/windsurf/mcp_config.json

Add Hronaut to Windsurf Cascade as a user-level Streamable HTTP server. The same entry remains available across local projects.

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

Open Cascade → MCPs, refresh the server list, and confirm that hronaut is connected. If authentication is enabled, copy the generated Windsurf entry from Hronaut Home; it reads the owner-only token with ${file:...} interpolation instead of publishing the secret in JSON. Official Windsurf MCP guide ↗

Open the focused Windsurf Cascade walkthrough →

Generic MCP client

Streamable HTTP

Use the standard transport and point the client directly at Hronaut.

{
  "name": "hronaut",
  "transport": "streamable-http",
  "url": "http://127.0.0.1:47812/mcp"
}