Aestheria vs zeroheight
zeroheight publishes the design system your team maintains, and serves it to agents. Aestheria, the design context layer, is a design system that arrives already written for machines, for the teams who never had one to publish.
Both ends of the same pipe.
zeroheight is where a design system gets documented, versioned, and adopted across a company, and its MCP server now serves that documentation to coding agents. If your team maintains a system and people need to read it, that is the job it does.
Which makes the pipe the uninteresting part of this comparison. Every serious tool in this category has an MCP server now. The question worth asking is what sits on the other end of it.
What the system has to contain.
A documentation platform serves what your team has written. That is exactly right when the writing exists, and it is the whole problem when it does not. Most teams shipping UI fastest with agents have no design system, which is usually why they are shipping fast, and an MCP over an empty system serves nothing.
Aestheria ships the payload: tokens with usage rules, components with their states and constraints, patterns, page templates, and six skills carrying the judgment between them. You edit it into your product rather than building a system first, then documenting it, then connecting it.
Where it lives matters too.
Aestheria is files. The kit unzips into your repository, the CSS imports from a CDN, and the MCP is one way in rather than the only one. Nothing about your design system stops working when a subscription lapses or a network call fails, which is a different risk profile from a hosted platform holding the source of truth.
If you already run zeroheight, keep it. Documentation for people and context for agents are not competing for one slot. The useful question is whether the thing your agents read carries your rules in a form they can act on.
| zeroheight | Aestheria | |
|---|---|---|
| Built for | Documenting and adopting your design system | Generating on-system UI with agents |
| Starting point | You bring the system | Ships complete, editable down to the token |
| Contents | What your team writes and maintains | 405 tokens, 37 components, 22 patterns, 63 templates |
| Judgment | Whatever your team documents | Six editable skills, loaded per task |
| Agent access | MCP over your documentation | MCP, repo files, or CDN import |
| Source of truth | The hosted platform | Files in your repository |
| Verification | Review and adoption metrics | validate_snippet on generated markup |
- 405 tokens
- 6 themes
- 37 components
- 27 charts
- 63 templates
Questions
Is Aestheria a design system documentation tool?
No. Documentation describes a system your team built; Aestheria is a system, written to be read by agents and edited by you. A team can run both, with docs for people and the layer for generation.
zeroheight has an MCP server. What is different here?
What it serves. An MCP is a pipe, and the pipe is no longer anyone's advantage. zeroheight serves the documentation your team wrote; Aestheria serves a complete system, including the judgment and a validation call, whether or not you had one to begin with.
What if we have no design system at all?
That is the case Aestheria was built for. The kit ships a complete one as starter context, so your agents have something specific to generate against on day one instead of after a quarter of design work.