ui-architect-mcp
Related Servers
Alternatives to ui-architect-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityFmaintenanceEnables AI-driven generation of UI components, full applications, and backend code across multiple frameworks (React, Vue, Angular, Svelte, HTML) with Figma integration and brand identity support.3865 npm2MIT- AlicenseAqualityDmaintenanceEnables AI-powered UI component generation from natural language descriptions, integrating with IDEs like Cursor and Windsurf.417,665 npmISC
- AlicenseAqualityAmaintenanceAI-native design engineering platform that converts Figma or live websites into a semantic design graph for code generation, and generates Figma designs from prompts with a self-improving director loop.28116 npm82MIT
- AlicenseNot gradedqualityBmaintenanceProvides design systems, UI prompts, and layout variation guidance to AI coding tools for generating better user interfaces.221 npm1,921MIT
- FlicenseBqualityDmaintenanceAI-driven tool that helps developers create beautiful UI components instantly through natural language descriptions, integrating with popular IDEs like Cursor, Windsurf, and VSCode.32-
- AlicenseAqualityCmaintenanceEnables AI-powered UI component generation from natural language descriptions, integrating with IDEs like Cursor, Windsurf, and VS Code.417,665 npmISC
TDQS
Scored across 7 tools
Each tool has a clear and distinct purpose tied to a specific phase in the design pipeline (analysis, planning, theme, component selection, component exploration, background generation, SEO audit). There is no overlap — even the two component tools (select_components and explore_components) are differentiated by source (built-in vs. community).
All tool names follow a consistent verb_noun pattern with underscores (e.g., analyze_project, design_theme, select_components). The naming is predictable and descriptive, making it easy for an agent to understand each tool's role.
With 7 tools, the set is well-scoped for a UI architecture design process. Each tool earns its place, covering the essential phases without redundancy or unnecessary complexity.
The tool surface covers the full design pipeline from analysis to SEO audit. However, the seo_audit description references a 'generate_full_page' tool that is not included, and there is no explicit review tool, leaving a minor gap in the workflow.