Windsurf Cascade browser MCP

Give Windsurf Cascade a browser that survives the task.

Local MCP endpoint

http://127.0.0.1:47812/mcp

Cloud agents cannot reach this computer's loopback endpoint. Cascade and Hronaut must run on the same computer.

Before you start

This page is for the legacy Cascade agent.

Current Devin Desktop documentation says Devin Local is the default agent for new Devin Desktop tabs. It uses Devin CLI configuration instead of the Windsurf-era Cascade file. For a new tab, follow the Devin Local browser MCP guide. Continue here only when the interface names the agent Cascade.

Step 1 · Connect

Connect Cascade.

Start Hronaut. Open Cascade's MCP settings and edit ~/.codeium/windsurf/mcp_config.json. The entry works across local projects.

Authentication off (default)

~/.codeium/windsurf/mcp_config.json

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

Authentication on

Read the owner token from its file

Turn on Require MCP authentication in Hronaut, then copy the generated Windsurf entry from Hronaut Home. Cascade supports file interpolation, so the secret can stay out of JSON.

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

Do not commit the resolved token, paste it into chat, or expose the owner-token file to another user.

Using the Windsurf plugin for JetBrains?

The Windsurf plugin for JetBrains documents a separate file, ~/.codeium/mcp_config.json. Open Settings → Tools → Windsurf Settings → Add Server and use the same serverUrl entry. Its published guide documents environment interpolation but not token-file interpolation, so use the exact authenticated snippet Hronaut Home offers for your client rather than inventing a secret format.

Step 2 · Verify

Check that it works.

Use a clean workspace for this check, before Cascade goes near a signed-in page.

  1. 1

    Cascade sees Hronaut

    Open Cascade → MCPs, refresh the server list, and confirm that hronaut is connected. A saved JSON file alone is not runtime proof.

  2. 2

    Hronaut sees Cascade

    Open Hronaut Home. The client should appear under Connections.

  3. 3

    Run a first browser task

    Ask Cascade: “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 visible first-check workspace shows Example Domain.

Security

Protect your signed-in sessions.

Turn on authentication. 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.

Review actions on signed-in sites. Use named workspaces for agent tasks and review actions against authenticated websites. Hronaut does not turn a local agent into a safe unattended credential broker.

Keep the endpoint local. Hronaut listens on loopback. Only a local client on the same computer can connect without additional networking.

Keep going

Next steps.

Give every durable browser job its own named workspace. It keeps cookies and storage apart from other workspaces and stays available to the next local agent task. Learn how to hand off a login safely.

Sources

Hronaut is an independent project and is not affiliated with or endorsed by Cognition, Devin, or Windsurf.