For Windsurf

Cascade edits across a codebase in one flow. Aestheria, the design context layer, is what keeps a multi-file flow reading as one product instead of several.

A multi-file flow spreads one wrong assumption.

Cascade is at its best when a change crosses files: a feature that touches a route, a table, a panel, and a form. Design context is what decides whether those four surfaces come back as one feature or as four dialects of it.

Without it, the agent makes one assumption about your spacing, your borders, and your states, and then applies it consistently everywhere in the flow. Consistency with the wrong reference looks like competence until someone opens two screens side by side.

Connect it to Cascade.

One config file, or the MCP marketplace in the Cascade panel:

{
  "mcpServers": {
    "aestheria": {
      "serverUrl": "https://mcp.aestheria.design/mcp"
    }
  }
}

After editing the config, fully quit and reopen Windsurf. Closing the window alone will not reload servers, which is the usual reason a freshly added server appears to do nothing.

One reference for the whole flow.

With the library connected, every file in the cascade resolves against the same tokens, the same components, and the same rules, rather than against whatever the first file happened to establish. The flow stays a flow, and the product stays one product.

The layer is not Windsurf-specific, so the same context serves whatever else your team runs. An engineer who switches editors next quarter takes the system with them.

• 405 tokens
• 6 themes
• 37 components
• 27 charts
• 63 templates

Questions

How do I connect Aestheria to Windsurf?

Add the server to `~/.codeium/windsurf/mcp_config.json` with `serverUrl` set to `https://mcp.aestheria.design/mcp`, or add it from the MCP marketplace in the Cascade panel. Then fully quit and reopen Windsurf.

I added the server and nothing happened.

Closing the window does not reload MCP servers. Quit Windsurf completely and reopen it, then ask Cascade to run `aestheria get_setup` to confirm the tools are live.

Does it work across a multi-file cascade?

That is the case it is for. The library answers per query rather than per session, so the tenth file in a flow resolves against the same system as the first.

Do I need an existing design system?

No. The kit ships a complete one as starter context, and every token, component, and rule in it is yours to edit.