UI Kit Aggregator MCP
Related Servers
Alternatives to UI Kit Aggregator MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.-
- 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.107,110 npmMIT
- FlicenseAqualityBmaintenanceEnables AI assistants to search a catalogue of plain HTML, CSS and JavaScript UI components and fetch each one's exact files, settings and framework integration instructions. Lets users add production-ready interface components by asking in natural language.221-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, understand, and generate code for design system components by syncing and indexing a component library.ISC
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search, inspect, and retrieve real UI components from existing component libraries, with ranked results, score explanations, licence and provenance details, and safe installation plans. It also surfaces similar components and higher-level UI patterns so agents can reuse existing interface code instead of generating it from scratch.38 npmMIT

WunderUI MCPofficial
AlicenseAqualityBmaintenanceEnables AI coding agents to build UI with a design system's tokens, component inventory and prop signatures, page templates, and starter snippets, while tracking free/pro availability and live-updating design data.11102 npm2MIT
TDQS
Scored across 5 tools
Each tool has a recognizable role in a discover→inspect→fetch→verify pipeline: list_sources, search_ui_kits, get_item, get_license, check_compliance. The only soft overlap is between get_license (reads license metadata) and check_compliance (judges a proposed use), which an agent could confuse when asking 'can I use this?'. The near-identical boilerplate text repeated in every description also makes the tools harder to skim apart, even though the core actions differ.
All five names follow a clean verb_noun snake_case pattern (list_sources, get_license, search_ui_kits, get_item, check_compliance). Verbs are chosen distinctly per action rather than reused vaguely. Fully predictable.
Five tools is well-scoped for a read-only aggregator: discover sources, search, fetch an item, read license, check compliance. No tool feels redundant or filler, and nothing essential is obviously missing from the count itself.
The surface covers the full lifecycle for a licensed UI-kit catalog: list sources, search with filters, fetch an item, inspect license, and gate usage via compliance. Minor gaps include no per-source browse/index tool (you must search blind with a query) and no token-status check tool, so agents must probe by fetching.