Skip to main content
Glama

Related Servers

Alternatives to UX Laws MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      An MCP server that provides comprehensive UX best practices covering accessibility, usability, UI patterns, design systems, performance, and more, enabling clients to analyze and generate UX-optimized code and recommendations.
      23
      58 npm
      29
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted design audit MCP server that reviews UI code against Nielsen's heuristics and an accessibility rubric, returning scores and fixable findings. It also enables verifying previously flagged issues against updated code.
      33 npm
      BSD 4-Clause "Original" or "Old"
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that audits websites for accessibility (WCAG 2.1 AA/EAA), performance, SEO, design quality, and mobile responsiveness, providing actionable scores, grades, and prioritized fixes.
      6
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for accessibility auditing that provides WCAG 2.2 criteria lookup, HTML remediation guidance, and automated documentation generation for UI components. It enables users to analyze code snippets for issues and generate professional accessibility audit reports.
      140 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      -

    TDQS

    B3.1/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool is clearly distinct, targeting a specific UX law or utility function (e.g., analyze_fitts_law, ux_checklist). The consistent 'analyze_' prefix for law-specific tools and descriptive names for utility tools (e.g., ux_detect_platform) eliminate ambiguity. No tools appear to overlap in purpose, making misselection unlikely.

    Naming Consistency5/5

    Tool names follow a highly consistent pattern: all law analysis tools use 'analyze_' + snake_case law name (e.g., analyze_aesthetic_usability), and all utility tools use 'ux_' + snake_case descriptive term (e.g., ux_list_laws). This uniformity across all 37 tools makes the set predictable and easy to navigate.

    Tool Count2/5

    With 37 tools, the count is excessive for a UX analysis server, especially since many tools (30 for individual laws) could be consolidated into a single configurable analysis tool. This bloats the interface and may overwhelm agents, as the core functionality (analyzing UX laws) is fragmented across many similar tools rather than being efficiently scoped.

    Completeness5/5

    The tool set comprehensively covers the UX analysis domain: it includes individual analysis for 30 specific laws, a full audit tool, law listing/info tools, platform detection/comparison, and checklists. There are no obvious gaps; agents can perform detailed analyses, get contextual information, and handle multi-platform scenarios seamlessly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues