Windsurf

Connect Forvibe MCP to Windsurf (Cascade) via mcp_config.json.

Updated 2026-05-12
2 min read

Windsurf's Cascade agent reads MCP servers from ~/.codeium/mcp_config.json. Streamable HTTP, SSE, and stdio transports are all supported, with optional OAuth on any of them.

Setup

1

Mint an API key

Open Settings → API Keys and create a key named e.g. "Windsurf on MacBook". Copy the fvk_live_… token shown once.

2

Open the raw MCP config

Two ways to reach the file:

  • Through Cascade UI: click the MCP icon (top-right of the Cascade panel) → scroll to the bottom → View raw config.
  • Directly: open ~/.codeium/mcp_config.json in any editor (create the file if it doesn't exist).
3

Add Forvibe

For remote HTTP MCP servers Windsurf uses serverUrl (not url):

json
{
  "mcpServers": {
    "forvibe": {
      "serverUrl": "https://www.forvibe.app/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FORVIBE_API_KEY}"
      }
    }
  }
}

Then export the key in your shell startup file so Windsurf can interpolate it:

bash
export FORVIBE_API_KEY="fvk_live_..."
4

Refresh Cascade

Cmd-Shift-P → Cascade: Refresh MCP servers. Or quit and reopen Windsurf.

Verify

Open Cascade and check the MCP panel — forvibe should show enabled with all tools listed. Try: "Pull the latest 5 unreplied reviews for my Forvibe project."

Windsurf supports OAuth for any of its transports if you'd rather not paste a static key. Leave the headers block out and Windsurf will trigger the browser consent flow on first connect.