Integration
Augment knows your codebase. Windcraft gives it your design language.
Augment Code is built around a context engine that understands large codebases. Understanding your code is not the same as knowing your design values, though — context tells it what exists, not what your brand blue is. Windcraft supplies the values over MCP.
Why codebase context is not a design system
Augment’s strength is retrieving relevant context from a big repo, which makes its edits well-informed about structure. But design values are not reliably inferable from context: seeing ten buttons does not tell the model which radius is canonical, and it will average toward something plausible. Without your tokens served as values, the generated UI drifts even when the agent understands the surrounding code perfectly.
How Windcraft plugs into Augment
Augment supports MCP natively. Add the Windcraft server through its MCP settings and Augment can call the design tools — tokens, contracts, patterns — alongside its own context engine, so generation is both context-aware and design-aware.
- Run npx windcraft init in your repo to generate the config.
- Add the Windcraft server through Augment’s MCP settings (Settings → MCP).
- Augment calls get_design_tokens / get_component_contract / get_page_pattern as it works.
- Run npx windcraft check to flag any drift before you commit.
Augment MCP server entry
{
"mcpServers": {
"windcraft": {
"command": "npx",
"args": ["windcraft", "mcp"]
}
}
}FAQ
- How is this different from Augment’s context engine?
- They are complementary. Augment’s context engine retrieves relevant parts of your codebase; Windcraft supplies your design values over MCP. One tells the model what your code looks like, the other tells it what your design system actually is.
- Augment already has lots of context — why serve tokens?
- Because context is for inference and tokens are exact. Seeing your components lets the model guess your radius; get_design_tokens returns the literal value, deterministically, so the guess is replaced by a read.
- 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.