> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fortressproductivity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Windsurf setup

> Connect Windsurf Cascade to Fortress MCP.

Use Windsurf when Cascade should read and update Fortress work.

## Add Fortress

Generate a **Windsurf** setup snippet in Fortress. Add it from **Windsurf Settings > Cascade > MCP Servers > View Raw Config**, or edit:

```text theme={"theme":"github-dark"}
~/.codeium/windsurf/mcp_config.json
```

The generated config uses Windsurf's remote HTTP shape:

```json theme={"theme":"github-dark"}
{
  "mcpServers": {
    "fortress-agent": {
      "serverUrl": "https://api.fortressproductivity.com/mcp?agent_id=<agent-id>",
      "headers": {
        "Authorization": "Bearer ft_<token>"
      }
    }
  }
}
```

Windsurf accepts either `serverUrl` or `url` for remote HTTP MCPs. Fortress emits `serverUrl` because Windsurf's examples call that out for remote HTTP servers.

## Verify

Refresh MCP servers in Windsurf, then ask Cascade to read `fortress://workspace/overview`.

## Secret handling

Windsurf supports environment and file interpolation in `headers`. For a long-lived local setup, prefer:

```json theme={"theme":"github-dark"}
{
  "headers": {
    "Authorization": "Bearer ${env:FORTRESS_TOKEN_AGENT}"
  }
}
```

See Windsurf's [Cascade MCP documentation](https://docs.windsurf.com/windsurf/cascade/mcp).