Windsurf Quick Start
Connect ToolPilot to Windsurf and start discovering developer tools in under 2 minutes.
Prerequisites
- Windsurf editor installed
- Node.js 18+ (for
npx)
Step 1: Add the MCP Server Config
Add the ToolPilot MCP server to your Windsurf configuration file:
~/.codeium/windsurf/mcp_config.json
1{
2 "mcpServers": {
3 "toolpilot": {
4 "command": "npx",
5 "args": ["-y", "@anthropic/toolpilot-mcp"]
6 }
7 }
8}
Config location
Windsurf stores its MCP configuration at
~/.codeium/windsurf/mcp_config.json. If the file doesn't exist yet, create it. You can also access it through Windsurf Settings → Cascade → MCP Servers.Restart Cascade
After editing the config, restart the Cascade panel (or reload Windsurf) to pick up the new MCP server.
Step 2: Try Your First Search
Open Windsurf's Cascade panel and ask about developer tools. ToolPilot handles discovery via MCP:
Example conversation
You: "I need a CI/CD tool that's easy to self-host, supports Docker-based
pipelines, and has good GitHub integration."
Windsurf (using ToolPilot):
→ Calls search_tools with your query
→ ToolPilot may ask: "Are you looking for a full platform or a lightweight runner?"
→ Windsurf answers via search_tools_respond
→ Returns ranked results:
1. Gitea Actions — Health: Active ★★★★★ (GitHub-compatible, lightweight)
2. Woodpecker CI — Health: Active ★★★★☆ (Docker-native, simple YAML)
3. Drone CI — Health: Stable ★★★★☆ (container-based, plugins)
4. Concourse CI — Health: Stable ★★★☆☆ (resource-based, declarative)Be specific
Include details like language, deployment model, and constraints. The more context you provide, the fewer clarification rounds ToolPilot needs.
Step 3: Explore Results
Each recommendation from ToolPilot includes:
- Health tier — Active, Stable, Slowing, or At Risk
- Graph context — Alternatives, companions, and dependencies
- Key metadata — Stars, license, language, and last release
- Match rationale — Why this tool fits your specific requirements
Ask follow-ups like “Compare Woodpecker and Drone CI” or “What monitoring tools pair well with this CI setup?”.
Step 4: Report Outcomes
After trying a tool, let Windsurf know how it went. This feeds back into ToolPilot's graph:
Feedback example
You: "Woodpecker CI was exactly what I needed — easy to set up and runs great."
Windsurf (using ToolPilot):
→ Calls report_outcome with tool="woodpecker-ci", outcome="adopted"
→ The graph learns from your feedback