A
licenseA
qualityD
maintenanceEnables 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.
10
6,787 npm
MIT
kodza
by kodza-dev
Related Servers
Alternatives to kodza
No user-submitted related servers found.
Related Servers
- 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.60 npmMIT
ui-layouts-mcpofficial
AlicenseBqualityBmaintenanceEnables AI assistants to search, understand, and retrieve UI components from ui-layouts.com through tools like search, documentation, metadata, and source code access.4370 npm34MIT- AlicenseAqualityBmaintenanceEnables AI coding assistants to search eight public UI and motion component catalogs, apply built-in license gating, and retrieve approved documentation, examples, or source code.517MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, understand, and generate code for design system components by syncing and indexing a component library.ISC
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to search, preview, and retrieve authentic production-ready React + Tailwind CSS bento grid components from 20 verified UI libraries and inject them into codebases.MIT
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
search_components is clearly for discovery and returns slugs, while get_component retrieves full details for one slug. Their purposes are complementary and non-overlapping, so an agent can easily choose the right tool.
Naming Consistency5/5
Both tools follow a consistent snake_case verb_noun pattern: search_components and get_component. The naming is predictable and readable.
Tool Count3/5
The server is intentionally minimal, but two tools is thin for a component library interface. The search/get split is coherent, though additional browse or category tools could reduce reliance on search nuances.
Completeness4/5
The surface covers discovery and full component retrieval, including code, API, keyboard behavior, dark-mode values, and install notes. Minor gaps exist around explicit category browsing and file-focused retrieval, but the core read-only workflow is covered.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues