Windsurf

Connect Cascade to the Vuesax catalog.

MCP & AI editors 1 min read

TL;DR · Cascade, once the config is right

  • Config lives in ~/.codeium/windsurf/mcp_config.json.
  • Remote servers use serverUrl, not url. This one trips everyone.
  • Older builds speak stdio only: bridge with mcp-remote.

Windsurf’s agent (Cascade) loads MCP servers from ~/.codeium/windsurf/mcp_config.json. You can also reach it from Settings → Cascade → MCP servers → View raw config.

Add the server

{
  "mcpServers": {
    "vuesax": {
      "serverUrl": "https://mcp.vuesax.com",
      "headers": {
        "Authorization": "Bearer vsx_your_key_here"
      }
    }
  }
}
serverUrl. This is the way. Windsurf uses serverUrl for remote HTTP servers, not url. A config copied from Cursor will silently fail to connect.

Save, then press Refresh in the MCP panel. The vuesax entry should list its tools.

Use it

YouUse the vuesax MCP: pull a card component and a badge into src/components/ui/, then build the project grid with them.

Cascade shows each tool call before it runs. Approve it once and it keeps going.

If Windsurf can’t reach an HTTP server

Older builds only speak stdio. Bridge it with mcp-remote:

{
  "mcpServers": {
    "vuesax": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.vuesax.com",
        "--header",
        "Authorization: Bearer vsx_your_key_here"
      ]
    }
  }
}

That runs a local proxy which forwards to the HTTP endpoint. Needs Node 18+ on your PATH.

Install the skill

YouCall get_vuesax_skill and save it to .windsurfrules

Cascade reads that file for every request in the workspace. See Skills.

Troubleshooting

Editing the config, then not pressing Refresh.
  • Tool count capped: Windsurf limits how many MCP tools are active at once. Disable servers you aren’t using if vuesax tools go missing.
  • 401: key missing, not vsx_…, revoked, or the account is not PRO.
  • Nothing at all: the JSON is invalid, or Windsurf was not refreshed after the edit.