Install in Windsurf

Install in Windsurf

slipstream's MCP server runs in Windsurf via the Cascade MCP host. You get the full sp_* toolset and the local dashboard. The Claude Code plugin surface (skills, slash commands, hooks, statusline) is not available here; the dashboard browser tab is the universal UI.

Requirements

• Windsurf 1.4 or newer with Cascade enabled.
• Node 20 or newer on your PATH.
• A local clone of slipstream, built once.

Check Node from the Windsurf integrated terminal:

node --version

Build the server once

git clone https://github.com/sarmakska/slipstream
cd slipstream
npm install
npm run build

This produces dist/mcp/index.js. Note the absolute path; you will paste it into the Windsurf config.

Locate the MCP config file

Windsurf reads Cascade's MCP servers from a per-user JSON file.

• macOS: ~/.codeium/windsurf/mcp_config.json
• Linux: ~/.codeium/windsurf/mcp_config.json
• Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

You can also open Settings → Cascade → MCP servers → Edit configuration, which opens the same file.

Paste the slipstream block

{
  "mcpServers": {
    "slipstream": {
      "command": "node",
      "args": ["/absolute/path/to/slipstream/dist/mcp/index.js"]
    }
  }
}

If the file already has an mcpServers block, add the slipstream key alongside the existing entries.

Restart Windsurf

Fully restart Windsurf. On startup Cascade spawns the slipstream MCP server over stdio and the dashboard server boots automatically.

Verify the tools appear

Open Cascade and ask:

list your MCP tools

You should see the 14 sp_ tools: sp_map, sp_symbol, sp_lines, sp_search, sp_search_memory, sp_timeline, sp_observations, sp_lessons, sp_savings, sp_budget, sp_dashboard, sp_remember, sp_recall, sp_mindmap.

Then ask Cascade to call sp_dashboard. It returns a 127.0.0.1 URL. Open it in your browser; the live dashboard fills in as the agent works.

Troubleshooting

• No tools listed. Settings → Cascade → MCP servers shows the resolved config path and a live status row per server. A red row exposes the server log.
• "command not found: node" in the server log. Cascade inherited a PATH without Node. Set an absolute path, for example "command": "/usr/local/bin/node" on macOS or "C:\\Program Files\\nodejs\\node.exe" on Windows.
• Server starts then exits immediately. Re-run npm run build in the slipstream clone; the path in args must point at a built dist/mcp/index.js, not the TypeScript source.
• Dashboard tab is empty. Ask Cascade to call sp_map first; the dashboard reflects MCP activity, so it stays quiet until a tool runs.
• Cascade does not call the tools. Confirm Write mode is on (not Chat mode). Chat mode will not invoke MCP tools.

---

SarmaLinux . sarmalinux.com . Repository