UI components with an MCP connection
Connect component discovery to an agent without turning the catalog into an unbounded code feed.
CurrentThe agent guesses a package or scrapes a visual gallery.Agents guess or scrape.
ProposedThe agent asks for matching cards, gets structured metadata, then requests the chosen component.Agents query, then fetch one component.
✓Read-only discovery first
✓Single catalog source of truth
✓Human review before product change
Where the alternative fits
Use the right tool for the job.
This page does not pretend one product replaces every other product. The deciding question is whether you are browsing, generating, or reviewing a change on a screen that already exists.
Try That UI difference
The decision stays attached.
The current state, proposed treatment, source, evidence, and keep or reject outcome travel together. That makes the result inspectable instead of becoming another disconnected screenshot.