uxloom
OfficialRelated Servers
Alternatives to uxloom
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create and manage consistent multi-screen UI designs through a token-efficient MCP interface, with design system tokens, components, flows, and visual review.35 npmAGPL 3.0
- AlicenseNot gradedqualityBmaintenanceDeploys AI user personas to validate user journeys at scale, surfacing UX friction before real users encounter it.1MIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to retrieve mode and stage guidance so they can lead users through a 9-stage design workflow, including questions, required artifacts, exit criteria, dependencies, pitfalls, rollback impact, and environment requirements. It helps non-designers turn ideas into buildable HTML/WPF design specs while keeping the human in control of confirmation and revisions.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to score live URLs against a 40-check design contract, validate DTCG tokens and Lottie animations, audit accessibility, and retrieve design-system contracts, catalogs, and review rubrics.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.150 npm30MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run deterministic API validation and UI DOM checks, verifying HTTP status codes, JSON schema fields, and page elements with programmatic proof instead of LLM guesswork.MIT
TDQS
Scored across 17 tools
Most tools map to a distinct lifecycle stage or object—brief, journey, screen, comment, audit—and the descriptions include explicit workflow hints that reduce confusion. The main ambiguity is among the validation/critique cluster (design_review, screen_critique, project_validate, coverage_report), but their scopes are differentiated enough for careful agents.
The set is consistently snake_case and mostly follows a <resource>_<operation> shape, with clear clusters like project_*, comment*, and design_*. Minor inconsistencies exist: comments_list vs comment_context vs comment_resolve mix plural/singular and some names use nouns rather than verbs (design_audit, coverage_report), but the overall pattern remains readable.
17 tools is slightly above the typical 3-15 range, but the domain genuinely spans briefs, screen and journey modeling, validation, review rounds, comment triage, audits, and coverage reporting. Each tool has a defensible role, so the count feels dense but not bloated.
The lifecycle is broadly covered: init, brief, define, import/export, validate, review, comment resolution, audits, and coverage reporting are all present. Minor gaps exist, such as no explicit delete tool or direct assumption-ledger reversal, though project_import can replace the whole project as a workaround.