Integration
Cline executes the plan. Windcraft keeps the design coherent.
Cline plans, runs commands, and edits files autonomously. The more it does per run, the further a single guessed value travels. Windcraft gives Cline a local MCP server so it reads your tokens and contracts instead of improvising them.
Why autonomous agents amplify drift
Cline works in steps — read, plan, edit, verify — across many files in one task. Each step reasons about the immediate change, so an off-token color chosen early gets repeated as the agent "stays consistent" with its own earlier mistake. The autonomy that makes Cline productive also means a design slip compounds without anyone in the loop to catch it mid-run.
How Windcraft plugs into Cline
Cline has native MCP support configured through its settings file. Add the Windcraft server and Cline can call the design tools during planning and editing, reading the exact values before it writes UI.
- Run npx windcraft init in your repo to generate the config.
- Add the Windcraft server to Cline’s MCP settings (cline_mcp_settings.json).
- Cline calls get_design_tokens / get_component_contract / get_page_pattern as it works.
- Run npx windcraft check to flag any drift before you commit.
Cline MCP settings (cline_mcp_settings.json)
{
"mcpServers": {
"windcraft": {
"command": "npx",
"args": ["windcraft", "mcp"]
}
}
}FAQ
- Does Cline call the Windcraft tools automatically?
- Once the server is registered, the tools are available to Cline; it calls them when a task involves UI, the same way it uses any MCP tool. You can also prompt it explicitly to fetch the contract or tokens for a component.
- Will this slow Cline down?
- No meaningfully — the tool calls hit a local server with a 60-second cache and respond in well under a tenth of a second. The time saved not redoing drifted UI dwarfs the per-call cost.
- 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.