No user-submitted related servers found.
Scored across 31 tools
The list_/get_/search_ pattern per resource (components, themes, tokens, functions, mixins, recipes, animations) gives each tool a clear resource+action target. Minor overlap exists where get_animation also returns a mixin record (blurring with get_mixin) and where read_llm_txt/read_contract/read_readme all return summary-style docs, but descriptions disambiguate these well.
Nearly every tool follows a clean snake_case verb_noun convention (list_themes, get_theme, search_themes, validate_theme, assemble_prompt). The read_* prefix is applied uniformly across all nine doc tools, forming a coherent sub-convention rather than an inconsistency.
31 tools is heavy and pushes past the 25-tool threshold where sets start feeling unwieldy. The breadth of the CSS library justifies many of them, but the nine individual read_* doc tools and parallel list/get/search triples for seven resource types could be consolidated (e.g. a single read_doc(name) tool).
Coverage is strong: list/get/search exist for components, themes, tokens, functions, and mixins, plus validation, size resolution, and prompt assembly. Minor gaps remain — animations and recipes have list/get but no search counterpart, and there is no create/update surface, though that fits a read-oriented reference server.
