Skip to main content
Glama
Better Design

Better Design

Related Servers

Alternatives to Better Design

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Equips coding agents with curated design rules, art directions, UI audits, component discovery, and reference guides so they can produce less generic, more polished interfaces in Claude Code, Codex, Cursor, and other MCP clients.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      118 npm
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to build professional websites using a curated component registry, WCAG-verified design systems and tokens, a human-in-the-loop visual editor, and real-browser Chromium QA that verifies rendered pages and iterates on fixes. It exposes deterministic design decisions, screenshots and evidence-backed quality scores as MCP tools over stdio or Streamable HTTP.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      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.
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Gives coding agents concrete, real product screens as inline references for unresolved layout, state, or interaction questions, plus licensed fonts and icons and the recorded design system behind a chosen web screen. Also bundles a token-free design workflow, diagnostics, and command playbooks that keep UI work grounded in the agent's own product.
      -

    TDQS

    A4/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools occupy clearly separate territory: design-system discovery/creation/config, icon search/install, per-framework implementation guides, and review gates each have distinct verbs and subjects. A few pairs still need the descriptions to separate them — get-ui-principle vs get-ux-principle, review-dashboard-structure vs finalize-dashboard-review vs review-ui-code, and find-design-system vs get-design-system-kit overlap enough that an agent could reach for the wrong one first. The heavy cross-references embedded in descriptions mitigate this, so confusion is possible but recoverable.

    Naming Consistency5/5

    Every one of the 48 names is kebab-case and starts with a verb (get-, find-, create-, review-, check-, set-, build-, read-, update-, install-, inspect-, extract-, plan-, render-, make-, send-, confirm-, preview-, finalize-, propose-, cut-, detect-). Noun suffixes are stable and predictable within families (get-*-guide, get-*-principle, find-* / install-* for icons, *-design-system for brand work). No camelCase, no mixed conventions, no vague standalone verbs.

    Tool Count2/5

    48 tools is far past a workable single-surface count; the server has grown into roughly eight sub-products (design systems, icons, framework guides, video/Remotion, Figma, review/verification, team rules, feature mapping, hosted sales assets). Individual tools are defensible, but an agent must triage 48 options including six review-related and nine *-guide retrieval tools before it can act. Splitting the review/verification cluster and the video cluster into separate servers would restore a usable surface.

    Completeness4/5

    The core lifecycle is unusually well covered end to end: discover or extract a design system, generate and poll it, read/write its config, install kits per target, pick and install icons, build, then verify with source review, comprehension, spacing, dashboard structure and a source-bound final receipt. Gaps are minor — no delete/archive operation for created design systems or installed icons, and no explicit tool to list the account's existing design systems beyond semantic search. Those are workarounds, not dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues