Skip to main content
Glama

Related Servers

Alternatives to Kaava

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to generate complete, deterministic design systems from a single brand color — harmonious palettes, font pairings, type and spacing scales, elevation shadows, responsive grids, motion presets, dark-mode themes, and WCAG contrast audits — and export them as CSS, JSON, Tailwind, or SCSS through natural conversation.
      10
      63 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Translates design tokens across platforms — extracts from Tailwind/CSS/Figma and generates native themes for Material 3, SwiftUI, and CSS variables with WCAG contrast validation.
      9
      106 npm
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to audit frontend source for generic AI UI patterns and WCAG 2.1 contrast failures, extract Design DNA from local stylesheets or live URLs, and export Tailwind v4 tokens. It also applies complete design presets to synchronize agent rule files and MCP configuration.
      2
      5
      683 npm
      36
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to search, resolve and audit DTCG design tokens — finding the token behind an intent or a hard-coded color/size, checking naming grammar, auditing CSS for hard-coded or unknown tokens, arbitrating semver, and previewing token additions as JSON Patch diffs. Writes are gated behind explicit confirmation plus an opt-in flag, so every change arrives as a reviewable proposal rather than an edit.
      7
      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

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct action: create, update, read tokens, full a11y audit, emit for stack, and single-pair contrast check. The audit vs check_contrast boundary is clearly explained (whole-system audit vs one-off pair check), so an agent can pick correctly.

    Naming Consistency4/5

    All tools share the kaava_ prefix and snake_case with verb-first naming (create_system, update_system, get_tokens, check_contrast). Two tools (kaava_audit, kaava_emit) drop the noun object, a minor deviation from the otherwise consistent verb_noun pattern.

    Tool Count5/5

    Six tools is well-scoped for a design-system generator: create/update lifecycle, token introspection, auditing, contrast check, and multi-target emission. No tool feels redundant or padding.

    Completeness4/5

    The surface covers create → update → inspect → audit → emit plus ad-hoc contrast checks, a solid lifecycle. The only notable gap is no delete/reset operation to remove kaava.json or clear overrides, which agents might occasionally need.