Local MCP endpoint

http://127.0.0.1:47812/mcp

Cloud Devin sessions cannot reach this computer's loopback endpoint. This guide is for Devin Local, including the default agent for new Devin Desktop tabs, running on the same computer as Hronaut.

Use the current agent

Configure Devin Local, not the legacy Cascade agent.

Current Devin Desktop documentation identifies Devin Local as the default agent for new Devin Desktop tabs. It reads Devin CLI configuration. The legacy Cascade agent keeps a different Windsurf-era file and schema, documented below only for existing Cascade users.

User-scoped setup

Add Hronaut as a Streamable HTTP server.

Start Hronaut, then use the command for an unprotected profile or add the equivalent user-level JSON. User scope is ~/.config/devin/mcp_config.json on macOS and Linux and %APPDATA%\devin\mcp_config.json on Windows.

Authentication disabled

Devin CLI

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

A URL selects Streamable HTTP automatically. This command intentionally contains no bearer token.

Equivalent user configuration

~/.config/devin/mcp_config.json

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

Authentication enabled

Read the owner token from its file

Enable Require MCP authentication in Hronaut, then copy the current token-file path from Hronaut Home into this user-only configuration. Devin supports file interpolation, so the token does not need to appear in JSON.

{
  "mcpServers": {
    "hronaut": {
      "url": "http://127.0.0.1:47812/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer ${file:/path/from-hronaut-home}"
      }
    }
  }
}

Do not commit the resolved token, paste it into chat, or copy it into a project-scoped .devin/mcp_config.json.

Devin Local 3.6 / v3000.3 moved MCP servers into dedicated mcp_config.json files. Current versions migrate older entries automatically. Follow the official Devin MCP configuration guide ↗ if your installed version differs.

Observable verification

Check configuration, connection, and browser behavior.

1 · Configuration

Inspect the saved server

devin mcp list
devin mcp get hronaut

The server should be enabled and point to Hronaut's loopback endpoint.

2 · Runtime

Watch Hronaut Home

Open Hronaut Home and confirm Devin appears under Connections. That is runtime evidence, not only a parsed configuration file.

3 · Browser task

Create an isolated 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.”

Expect a visible first-check workspace showing Example Domain.

Existing Windsurf users

Legacy Cascade uses a different file and field name.

Only use this for the legacy Cascade agent. Its current documentation uses ~/.codeium/windsurf/mcp_config.json and accepts serverUrl for remote HTTP MCP. Devin Desktop's documentation says new tabs default to Devin Local, so new setups should use the Devin CLI configuration above.

Legacy Cascade

~/.codeium/windsurf/mcp_config.json

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

Cascade also documents ${file:/path} interpolation for protected headers. See the official legacy Cascade MCP guide ↗.

Security and reachability

Local browser control stays local.

Hronaut listens on loopback. Devin Local on the same device can connect; a cloud Devin session, another computer, or a container without host-loopback access cannot. Authentication is off for a new Hronaut profile, so any process running as your user can control it. Enable authentication for sensitive signed-in profiles and keep the owner-token file private.

MCP tools default to approval in Devin. Review requested browser actions before allowing them, especially in authenticated workspaces.

Primary sources

Configuration and product-boundary evidence.

Keep the browser; change the task

Use a named Hronaut workspace for every durable browser job.

Named workspaces isolate cookies and storage from the human Default workspace while remaining available to the next local Devin task—or another compatible local MCP client.