Integration
Windsurf writes the flow. Windcraft holds the design language.
Cascade is built to reason across many files at once — that reach is the point, and the risk: one guessed radius propagates through a whole flow. Windcraft gives Windsurf a local MCP server to read tokens and contracts from instead of inventing them.
Why Cascade output drifts
Windsurf’s Cascade plans and edits across files in a single run. Each step reasons about the change in front of it, not the spacing scale three files back, so a plausible-but-off blue or an ad-hoc radius spreads across everything the flow touches. Memories and rules help, but they are prose the agent re-interprets each turn — it never had your exact values to read, only descriptions of them.
How Windcraft plugs into Windsurf
Windcraft runs a local MCP server. You add it to Windsurf’s MCP config once, and from then on Cascade can pull the exact tokens, the component contract, and the page pattern before it writes — no prose interpretation in the loop.
- Run npx windcraft init in your repo to generate the config.
- Add the Windcraft server to ~/.codeium/windsurf/mcp_config.json (or via the Windsurf MCP settings UI).
- Cascade calls get_design_tokens / get_component_contract / get_page_pattern as it works.
- Run npx windcraft check to flag any drift before you commit.
Windsurf MCP config (~/.codeium/windsurf/mcp_config.json)
{
"mcpServers": {
"windcraft": {
"command": "npx",
"args": ["windcraft", "mcp"]
}
}
}FAQ
- Is Windcraft the same as Windsurf?
- No — the names are close but the tools are not. Windsurf is an AI editor that writes code. Windcraft is the design layer Windsurf reads from over MCP, so the UI Cascade generates stays consistent across files. You use them together.
- Does it work with Cascade’s multi-file edits?
- That is exactly where it earns its keep. Because Cascade touches many files in a run, a single guessed value spreads fast. Windcraft gives it the real tokens and contracts to read before each edit, so the reach works for you instead of amplifying drift.
- Does my source code leave my machine?
- No. The MCP server and analyzer run locally. Only metadata — tokens, contracts, rule violations — is ever synced to the cloud.