Skip to main content
Glama

Related Servers

Alternatives to ai-design-expert

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      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.
      222 npm
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides source-backed design context, route card validation, contract generation, critique and verification reports, evidence packages, Penpot change plans, and anti-repeat checks for design workflows. Does not directly mutate Penpot, but consumes read-only Penpot snapshots.
      8 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides deterministic, read-only design knowledge for AI coding agents to help them choose visual directions, plan UI states, and compose design tokens, all without network access.
      6
      12 npm
      4
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enforces design systems and vocabulary via ontology checks, candidate scanning, linting, and structural search across repositories.
      7
      43
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the design pipeline: requirement analysis, token extraction, design generation, and visual audit. Input types and outputs are clearly differentiated, leaving no ambiguity about which tool to use.

    Naming Consistency5/5

    All four tools follow a consistent snake_case verb_noun pattern: analyze_requirement, extract_tokens, generate_design, audit_visual. The naming is predictable and uniform throughout.

    Tool Count5/5

    Four tools map cleanly onto a coherent design workflow. The count sits well within the 3-15 sweet spot, and each tool has a clear, non-redundant role.

    Completeness4/5

    The surface covers the full end-to-end workflow: parse requirements, extract tokens, generate a design, and audit the visual result. A minor gap exists in that there is no explicit tool to refine or fix the design based on audit findings, though an agent could work around this by re-invoking generate_design.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues