wellworn

Windsurf

The Cascade mcp_config.json entry, the serverUrl field name, and the 100-tool ceiling.

Windsurf keeps MCP servers in ~/.codeium/windsurf/mcp_config.json, under an mcpServers object. Cascade's documented field for a remote server is serverUrl; url is also accepted.

Without a key

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "wellworn": {
      "serverUrl": "https://mcp.wellworn.dev/mcp"
    }
  }
}

With a key

headers is a flat object of header names to values.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "wellworn": {
      "serverUrl": "https://mcp.wellworn.dev/mcp",
      "headers": {
        "Authorization": "Bearer ww_your_key"
      }
    }
  }
}

The file is not in the repository, so a pasted key stays on your machine. It is stored in plain text.

Confirm it works

Click the MCPs icon in the top right of the Cascade panel, then pick Wellworn to see its tools and toggle them. Eight should be listed: recommend, compare, alternatives, traps, skill, design, docs, submit_trap.

What breaks

Cascade reaches at most 100 tools at a time across every server. Adding Wellworn to a workspace that already runs several large servers can push you over that line, and the symptom is a tool that exists in the panel but is never called. Turn off tools you are not using from the same panel.

Windsurf does not reload mcp_config.json on its own. Press refresh in the MCPs panel after every edit.

Verified 2026-09-08 against docs.devin.ai

If your build predates remote MCP support, run the server through the stdio bridge instead:

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "wellworn": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.wellworn.dev/mcp"]
    }
  }
}