A
licenseA
qualityC
maintenanceProvides AI coding assistants with on-demand access to component specs, test scenarios, accessibility requirements, and build guides from the Web UI Component Specification.
10
MIT
evo-marko
by agliga
Related Servers
Alternatives to evo-marko
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides AI assistants with tools to grade, generate, and validate UI components against the components.build specification. Supports searching documentation, checking compliance, and generating framework-agnostic accessible components.1141 npmApache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides AI assistants with access to WordPress Design System component information and design guidance.9GPL 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.9MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to retrieve React, Svelte, Vue, and React Native component source code, demos, blocks, and metadata for building UIs in AI-powered development workflows.106,797 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access documentation of Vue UI components, including props, events, and slots, for generating correct usage code.7MIT
TDQS
A3.9/5.0
Scored across 8 tools
Disambiguation4/5
Each tool has a recognizable, mostly distinct role: list/search for discovery and get_* for retrieval, with migrate_from_ebayui and search_icons clearly specialized. There is mild overlap between list_components (free-text filter) and search_docs (which also indexes component attributes/examples), and between get_component and get_doc, but the descriptions give clear guidance on when to use which.
Naming Consistency4/5
Six of eight tools follow a clean verb_noun snake_case convention (list_components, get_component, search_docs, get_doc, list_docs, search_icons). The outliers are index_info (noun-only) and migrate_from_ebayui (verb_from_noun), which are readable but break the pattern slightly.
Tool Count5/5
Eight tools is well-scoped for a documentation/component reference server, with a balanced discovery (list_*, search_*) and retrieval (get_*) split plus two niche helpers. Every tool has a plausible job; nothing feels redundant or missing at the count level.
Completeness4/5
The surface covers the full read-only lifecycle of the domain: discovering components/docs/icons, retrieving details, searching full text, checking index provenance, and mapping Marko 5 to 6. Minor gaps remain, such as a dedicated way to browse changelogs or accessibility guidance independently of get_component, but these are reachable via existing parameters.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues