Documentation
Windsurf
Connect Milkey to Windsurf through the MCP UI or the raw `mcp_config.json` file.
Windsurf supports remote HTTP MCP servers directly, which makes Milkey straightforward to wire into Cascade-based coding workflows.
You can add the server through the Windsurf MCP UI or edit the raw config file directly when you want a shareable, reviewable setup.
Configure Windsurf
The client-specific work here is mostly about where the config lives and which field names the client expects.
- Use the MCP panel inside Windsurf for the easiest setup and server health checks.
- For a manual setup, edit `~/.codeium/windsurf/mcp_config.json` and add Milkey as a remote server.
~/.codeium/windsurf/mcp_config.json
{ "mcpServers": { "milkey": { "serverUrl": "https://mcp.vexelityai.com/mcp", "headers": { "Authorization": "Bearer mk_sk_your_api_key_id_your_secret" } } }}Verify the connection
- Open the Windsurf MCP list and make sure Milkey is installed and enabled.
- Check that the server is healthy and that the relevant Milkey tools are exposed.
- Run a short prompt in Cascade that should clearly depend on Milkey rather than generic coding advice.
Test prompt
Use Milkey to fetch the right skill for setting up durable Vercel workflows in this project and summarize the main architecture guidance.Operational tips
- Windsurf caps the total number of enabled tools across MCP servers, so disable unused tools on other servers if Milkey tools do not appear.
- If your team uses Windsurf admin allowlists, make sure the Milkey remote URL is approved before rolling this out broadly.