Skip to main content

Windsurf with Verdictan

Windsurf Cascade supports remote streamable HTTP MCP servers. This makes Verdictan tools available to Cascade. It does not reroute Windsurf's hosted model traffic.

Configure the remote MCP server​

In Windsurf, open Settings → Tools → Windsurf Settings → Add Server. Then use View Raw Config. This method does not use a config-file path that can change between Windsurf releases.

{
  "mcpServers": {
    "verdictan": {
      "serverUrl": "https://<published-hostname>/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VERDICTAN_MCP_TOKEN}"
      }
    }
  }
}

Before you launch Windsurf, set the variable:

export VERDICTAN_MCP_TOKEN="<client-api-token>"

After you save the config, refresh the MCP list. Enable only the Verdictan tools that are necessary for your workflow. For Team and Enterprise plans, make sure that an administrator allows this server in Windsurf's MCP controls.

See Windsurf's Cascade MCP documentation for the UI, allowlist, and interpolation rules.

Model-traffic boundary​

MCP configuration governs MCP tool calls only. Do not infer that Cascade chat or completion prompts traverse Verdictan. Verify each independently supported custom model endpoint with verdictan events tail --follow.

Next steps​