Windsurf Setup
Connect a paso MCP server to Windsurf.
Set up paso as an MCP server in Windsurf.
1. Install paso
npm install -g usepaso
Or use it locally with npx.
2. Connect
Run this from the directory containing your usepaso.yaml:
usepaso connect windsurf
Added "Sentry" in Windsurf config.
Config: ~/.codeium/windsurf/mcp_config.json
Restart Windsurf to connect.
Unlike Cursor and VS Code, Windsurf’s config is global, not per-project. paso writes to ~/.codeium/windsurf/mcp_config.json on macOS and Linux, or %APPDATA%\Codeium\Windsurf\mcp_config.json on Windows.
To remove the server later: usepaso disconnect windsurf.
3. Restart Windsurf
Quit and relaunch Windsurf. The MCP server starts automatically.
Verify Setup
Open the Windsurf AI panel and look for your paso capabilities in the tools section. Try calling one to verify.
Multiple Servers
Run usepaso connect windsurf from each service’s project directory. paso adds each entry to the same global config.
# In /path/to/sentry/
usepaso connect windsurf
# In /path/to/stripe/
usepaso connect windsurf
To remove a server: run usepaso disconnect windsurf from that service’s directory.
Troubleshooting
Server doesn’t appear in Windsurf.
Restart Windsurf completely. Run usepaso validate to confirm the declaration is valid.
“command not found”.
Use npx usepaso serve (no global install needed).
Auth failures (401).
Set USEPASO_AUTH_TOKEN in your shell or in a .env file next to your usepaso.yaml. Run usepaso doctor to check your setup end-to-end.
Server crashes on start.
Run usepaso serve directly in a terminal to see the error output. Run usepaso validate to check for declaration errors.
Windsurf can now reach your API.
Your capabilities are live in Windsurf. Try calling one in the AI panel.
Next, you might want to:
- Quick Start. create your first declaration
- Testing Capabilities. test before connecting to agents
- Claude Desktop Setup. connect to Claude Desktop
- Cursor Setup. connect to Cursor