Integration
Roo Code switches modes. Windcraft keeps one design language across them.
Roo Code runs as an autonomous agent with distinct modes for architecting, coding, and debugging. Each mode reasons differently, but none of them knows your tokens. Windcraft gives Roo a local MCP server so the design values are constant across every mode.
Why multi-mode agents drift
Roo Code’s strength is switching behavior per task — plan in one mode, implement in another. But a design value guessed while "coding" is not reconciled with one guessed while "architecting"; each mode improvises UI from priors. The mode system organizes how Roo thinks, not what your brand blue is, so consistency still has to come from a source outside the agent.
How Windcraft plugs into Roo Code
Roo Code supports MCP servers through its settings. Register Windcraft once and every mode can call the design tools, so whether Roo is planning a feature or writing a component it reads the same tokens and contracts.
- Run npx windcraft init in your repo to generate the config.
- Add the Windcraft server to Roo Code’s MCP settings.
- Any mode can call get_design_tokens / get_component_contract / get_page_pattern.
- Run npx windcraft check to flag any drift before you commit.
Roo Code MCP settings (mcp_settings.json)
{
"mcpServers": {
"windcraft": {
"command": "npx",
"args": ["windcraft", "mcp"]
}
}
}FAQ
- Do all of Roo’s modes get the design tools?
- Yes. The MCP server is registered at the workspace level, so any mode that can call tools — code, architect, and custom modes — can fetch your tokens, contracts, and patterns.
- Is this different from a custom mode prompt?
- Yes. A custom mode prompt is prose the model interprets. Windcraft serves machine-readable values over MCP — read, not interpreted — and the analyzer enforces them on the way out.
- Does my source code leave my machine?
- No. The MCP server and analyzer run locally. Only metadata — tokens, contracts, rule violations — is synced to the cloud.