Skip to main content
Glama

Related Servers

Alternatives to WunderUI MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      It lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.
      6
      206 npm
      202
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.
      13 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents to absorb UI references into perceptual design tokens, semantic responsive layout skeletons, motion physics parameters, and zero-dependency multi-framework components, while auditing WCAG contrast, touch targets, reduced-motion guardrails, and layout stability.
      6
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation3/5

    Most tools are clear, but three code-example tools overlap heavily: list_templates (full pages), get_starter (compositions), and get_block_source (Pro block source) all answer a vague 'show me an example' request. get_design_md also duplicates the content of get_tokens, get_instructions and list_components, which the description acknowledges but still creates a routing decision for the agent.

    Naming Consistency5/5

    Every tool follows a strict list_/get_ prefix with a snake_case noun object (list_components, get_component, get_tokens, get_skill, get_block_source). The pattern is predictable and the singular/plural distinction cleanly separates listing from fetching a single item.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range for a design-system server. Each tool maps to a distinct artifact type (components, tokens, templates, starters, skills, blocks, library meta) and none feel redundant or padded at the count level.

    Completeness4/5

    The surface covers the full read-only lifecycle an agent needs: discovery (list_components), detail (get_component), theming (get_tokens), guidance (get_instructions/get_design_md), code scaffolds (templates/starters), and skills/blocks. Minor gap: there is no tool to retrieve a single component's raw source (only Pro block source), so an agent may still have to write component internals by hand.