No user-submitted related servers found.
Scored across 33 tools
Every tool targets a distinct resource and action: list/get/search per entity type (themes, mixins, functions, tokens, components, recipes), with specialized tools for validation, building from tokens, and reading documentation. No two tools overlap in purpose, even within the same entity—get_theme returns a theme, validate_theme checks CSS, and theme_from_tokens generates from tokens.
Tool names follow a consistent verb_noun pattern using lowercase snake_case. Verbs like list, get, search, validate, read, assemble, and resolve are uniformly applied; plural nouns are used for list/search, singular for get. The pattern is predictable and immediately understandable.
With 33 tools, the count exceeds the typical 3–15 range, but the server covers a broad CSS framework with many distinct resource types (themes, mixins, functions, tokens, animations, components, recipes, docs). Each tool serves a unique purpose, and the high count is justified by the scope, though it borders on heavy.
The tool surface comprehensively covers the domain: theme operations (list, search, get, validate, build), introspection of mixins/functions/tokens/animations/components/recipes, documentation access, and utility helpers (assemble_prompt, resolve_size). No significant gaps exist for an information-retrieval and assistance MCP server.
