The problem
Every project re-implements the same button, card and form. Components live in old repos nobody remembers, and an AI asked to build UI invents its own instead of using yours.
Premium · à la carte
Components
A shared React library with live previews.
Your reusable React components, catalogued with live previews — a library both your team and your AI build from.
Library
React components
Reusable components — the standard library plus your org's own, previewed live and ready to copy.
Search component, tag or description…
AllStandard libraryMy org
The actual Components module — same theme, same layout as the app. Example data.
On the Cloudflare side
- The library lives in the platform database; components are token-aware TSX that your AI writes over MCP and that Build composes into Workers deployed to your account.
The problem and how sSystm solves it
How sSystm does it
sSystm catalogues your React components with live, rendered previews. Your team browses and reuses; your MCP-connected AI reads the same library and composes with your components instead of inventing new ones.
What Components gives you
Built deep, so the module actually carries the weight of real client work.
01
Live component previews
Every component renders live in the catalogue — see the real thing, not a screenshot.
02
Token-driven styling
Components pull from your Design System tokens, so the library is always on-brand.
03
One library, every project
Stop re-implementing the same UI. The library is shared across your whole workspace.
04
MCP write surface
Your AI reads the library and writes new token-aware components with sstm_component_create — they render live for your team to review.
Components on the MCP surface
The exact tools and resources your MCP-connected AI gets for this module — verbatim from the live server.
Tools · write
2sstm_component_createsstm_component_updateResources · read
3sstm://componentssstm://component/{id}sstm://component/recipeYour AI, via MCP
Your AI builds UI with your components, not around them. It reads sstm://component/recipe for the token vocabulary, then writes self-contained, token-aware TSX straight into the shared library — rendered live in the catalogue.
How the human gate worksReady to put Components to work?
Join the waitlist — when your spot opens, your workspace is provisioned on your own account and you switch on the modules you need.