Skip to content

Connect Windsurf to Willder

Codeium's AI editor (Cascade).

Transport: Streamable HTTP · Auth: Authorization: Bearer <capability token> · Endpoint: https://willder.ai/api/mcp

Half of this row is verified, and the two halves are different claims. The server's half passes: on 2026-10-05, against deployed commit 2eed3f05, npx tsx scripts/mcp-client-probe.ts --client=windsurf --transport-only reached https://willder.ai/api/mcp using Streamable HTTP with the exact Authorization header this page commits, and the initialisation sequence, tools/list and one scoped memory_query all answered, with an absent token and a wrong token both refused. The client's half is unrun. Nobody has run this client against Willder, so nothing here claims it works. Why: Windsurf is a desktop app, and its Cascade MCP screen is only visible in its own window. That needs a person's run recorded in manual-runs.json, naming who ran it, when, and on which commit — see the index.

Get a token

Open Access → Tokens in your Willder workspace and issue a capability token for the narrowest scope that answers your questions. The value is shown once; only its hash is stored. Keep it in the client's secret storage or an environment variable — never in a committed file, a prompt or a screenshot.

Terminal
export WILLDER_TOKEN='<your capability token>'

Config file

~/.config/devin/mcp_config.json on current builds (Windsurf's documentation now lives under Devin Desktop and names that path); older Windsurf builds read ~/.codeium/windsurf/mcp_config.json. Confirm the path your build reads in Settings → Cascade → MCP.

JSON
{
  "mcpServers": {
    "willder": {
      "serverUrl": "https://willder.ai/api/mcp",
      "headers": { "Authorization": "Bearer ${env:WILLDER_TOKEN}" }
    }
  }
}

Name your task (optional). Add "X-Willder-Task": "${env:WILLDER_TASK}" to headers and export WILLDER_TASK (a ticket key or branch name) before starting Windsurf: the first result of each session then leads with what earlier sessions of that task decided and wrote.

Verify the connection

Settings → Cascade → MCP shows willder with a green status and its tools listed.

Notes

The key is serverUrl, not url.

See the index for the other clients and mcp/README.md for the tool surface and the token rules.