Summary
The model answers with the library's actual component source instead of improvising a rating widget that looks close.
The catalogue is addressed by group, not by keyword: there is no search tool, so a request is served by picking getRatings or getProductCards and reading what comes back. That makes the two index tools the entry point rather than a nicety, since getUIComponents and getUIBlocks are what tell you which group a name lives in. Components and blocks stay separated all the way through, which matters when a page section and a primitive share a word like review.
What it is
A catalogue server for the stackzero-labs/ui library, where each of the 12 tools returns the implementation details for one named group of components or blocks.
What you get
- Two indexes to start from: getUIComponents lists the library's components and getUIBlocks lists its blocks.
- Rating and feedback widgets: getRatings covers star-rating-basic, star-rating-fractions, upvote-rating-basic, upvote-rating-animated, face-rating-basic and face-rating-gradient.
- Commerce primitives: getProducts covers price-format-basic, price-format-sale, quantity-input-basic, variant-color-selector-basic, variant-selector-basic, variant-selector-images and variant-selector-multiple, and getInputs covers input-icon and phone-number-input-basic.
- Media components: getImages covers image-viewer-basic, image-viewer-motion and image-carousel-basic.
- Storefront blocks: getProductCards covers product-card-01-block through product-card-13-block and getProductVariants covers product-variant-01-block through product-variant-05-block.
- Supporting page sections: getBanners covers banner-01-block through banner-12-block, getReviews covers review-01-block through review-10-block, getAddresses covers address-01-block and address-02-block, and getCarts covers cart-01-block.
Requirements
Nothing to supply — no account and no key.
Setup effort
One command — npx -y @stackzero-labs/mcp@latest