agy-ui-mcp
Related Servers
Alternatives to agy-ui-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceGenerates frontend UI code from text descriptions, screenshots, or iterative refinement using Gemini 2.5 Flash.2-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to act like a senior UI/UX team by reading an existing site's design DNA and tokens, proposing distinct art directions and motion mechanics that fit the brief, and validating changes in a live headless Chromium browser. Provides per-element accessibility and performance auditing (WCAG 2.2 contrast, focus, clipping, phone-menu behavior, LCP/CLS) at multiple viewport widths, plus baseline capture, before/after comparison, and one-command rollback for safe redesigns.561 npm2MIT
- AlicenseAqualityAmaintenanceOrchestrates full-stack frontend engineering—from intent discovery and design genome generation to automated multi-viewport QA—through JSON-RPC tools for AI agents.732 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI to capture, compare, and automatically patch frontend code against reference designs, achieving pixel-perfect fidelity without manual CSS tweaking.9 npm11MIT
- AlicenseAqualityAmaintenanceEnables AI agents to conduct UX reviews of web applications, detecting and fixing AI-generated design and usability issues while preserving the original style.1824 npm2MIT
- AlicenseAqualityDmaintenanceLets AI agents visually inspect web elements, test CSS edits in real-time, and iterate until pixel-perfect, functioning like browser DevTools for debugging UI issues.12 npm1MIT
TDQS
Scored across 3 tools
Each tool targets a distinct phase: ui_init configures the project, ui_implement applies changes, and ui_review critiques without mutating. There is no meaningful overlap in purpose, despite sharing some arguments like project_dir and target_route.
All tools follow a consistent ui_<verb> pattern in snake_case. The verbs init, implement, and review are clear and predictable, making tool selection straightforward.
Three tools are well-scoped for the server's setup-implement-review lifecycle. Each tool earns its place, and the count is comfortably within the ideal range for a focused MCP server.
The tool surface covers the full intended workflow: initialize a scope, implement UI changes, and review the result against design and accessibility criteria. ui_init's overwrite option and ui_implement's apply flag also provide sensible config-reset and dry-run paths.