agid-llm-ui MCP Server
Related Servers
Alternatives to agid-llm-ui MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn unofficial MCP server that gives AI assistants structured access to Italy's Design System .italia, including components, design tokens, usage guidelines, and GitHub issues, updated nightly.1735 npm4BSD 3-Clause
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.-
- AlicenseAqualityDmaintenanceMCP server that provides UI5 Web Components documentation and integration guides for AI assistants.4192 npm19Apache 2.0
- FlicenseAqualityNot gradedmaintenanceMCP server enabling AI agents to search, retrieve details, and compare UI components from 13 popular UI libraries.3-
- AlicenseNot gradedqualityDmaintenanceA comprehensive template for building MCP servers that expose UI component registries and design systems to AI assistants. It enables users to browse, fetch, and retrieve implementation details from registries following the shadcn/ui format.20 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for AI-powered component generation - analyze designs, generate components, and create implementation instructions.3 npm4MIT
TDQS
Scored across 9 tools
Most tools are clearly distinct: list_webcomponents vs list_components target different systems, and search_component/get_component_code, list_recipes/get_page_recipe form clear pairs for the Bootstrap Italia side. However, list_webcomponents and get_webcomponent, and search_component vs list_components, have some overlap in purpose that could cause minor misselection (e.g., when to use list vs search).
Tool names follow a mostly consistent verb_noun pattern (list_*, get_*, search_*, validate_). Minor deviations exist where list_webcomponents and list_components both serve listing roles but across different systems, and web components use 'list_webcomponents'/'get_webcomponent' (singular/plural inconsistency) vs the Bootstrap Italia 'list_components'/'get_component_code' pattern.
Nine tools is a well-scoped count for a design-system UI generation server. Each tool fills a distinct role: listing/discovering components, retrieving component code, recipes/pages, accessibility rules, and validation. No redundancy or bloat.
The tool surface covers discovery, retrieval, page composition, accessibility rules, and validation—a complete UI-generation workflow with no dead ends. Minor gaps exist, such as no tool to combine/assemble multiple snippets into a larger page, but the recipe tools partially cover this.