IntegrationsPer-client guides
Windsurf + Vaner (MCP)
Connect Windsurf to Vaner over MCP for predictive, repo-grounded context.
Windsurf supports the
Model Context Protocol out of the box.
Point it at vaner mcp and Vaner will serve scenario-ranked context to your
agent before every prompt.
Install
If you haven't installed Vaner yet:
curl -fsSL --proto '=https' --tlsv1.2 https://vaner.ai/install.sh | bash
vaner init --path .Connect Windsurf
Path: ~/.codeium/windsurf/mcp_config.json
{ "mcpServers": { "vaner": { "command": "uvx", "args": ["--from","vaner[mcp]","vaner","mcp","--path","."] } }}Verify
Restart Windsurf. Open Cascade and confirm the Vaner tools appear when prompting about this repo.
Upstream docs
https://docs.windsurf.com/windsurf/cascade/mcp
Verify
Restart Windsurf. Open Cascade and confirm the Vaner tools appear when prompting about this repo.
If Windsurf reports the server as failed, run vaner mcp --path .
manually in a terminal and read the error. The most common failure is a
missing backend API key — confirm with vaner config show.
What this unlocks
- Cascade pulls Vaner scenarios before drafting a plan, reducing thrash on large repos.
- Works alongside Windsurf’s built-in memory — Vaner supplies the structural context.
- Switch repos without restarting Windsurf; Vaner scopes itself to
--path.
See also
- The full Connect your client guide.
- Backends for picking the model Vaner ponders with.
- Upstream docs: https://docs.windsurf.com/windsurf/cascade/mcp.