uxui-principles
Related Servers
Alternatives to uxui-principles
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for VertaaUX.ai — run UX & accessibility audits, generate fixes, and monitor quality from your LLM or IDE. 38 tools covering the full audit-to-fix lifecycle across 7 UX categories.2969 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that works with Mobbin — 600k+ real app screens and flows from 1,100+ apps. Search screens, browse flows, grab palettes, build better UI without leaving Claude.6ISC
- AlicenseNot gradedqualityDmaintenanceMCP server for design decisions during a build, providing live UI/animation library docs (via llms.txt) and a curated knowledge base of UX laws and UI conventions. It enables agents to look up real component APIs and apply design best practices, running locally via stdio or hosted on Vercel.6 npmMIT
- AlicenseAqualityCmaintenanceMCP server providing UX insights from Vitaly Friedman as searchable tools for any LLM.415 npm4MIT
- AlicenseNot gradedqualityDmaintenanceA remote MCP server exposing uxspot.io's curated UX glossary, AI tools directory, checklists, and Learn UX curriculum as callable tools. Enables AI assistants to search for UX terms, tools, and checklists via natural language.2MIT
TDQS
Scored across 13 tools
Most tools target clearly distinct resources: principles (get/list/search), smells (get/list/detect), flows (get/list), and checklists/audit. The main overlap is between detect_smell, suggest_fix, and audit_interface, since suggest_fix internally detects a smell and audit_interface is described as a superset; descriptions do disambiguate them but an agent may still hesitate on which to call. get_flow_principles vs get_principle is also mildly confusable by name despite different purposes.
All 13 tools follow a consistent verb_noun snake_case pattern (get_, list_, search_, detect_, suggest_, generate_, audit_) with singular/plural nouns used logically for single-item vs collection operations. No mixing of conventions or casing styles.
13 tools is well within the 3-15 sweet spot and each maps to a distinct capability across principles, smells, flows, and auditing. Nothing appears redundant or padding the surface.
The surface covers the core lifecycle: browse/search/fetch principles, get prompts, browse/detect smells and get fixes, list/get flows, generate checklists, and audit an interface. Minor gaps exist — no way to enumerate the prompt library directly and no tool to list principle parts/tags as a standalone operation — but these are workable via list_principles and search_principles.