Skip to main content
Glama
kenneives

design-token-bridge-mcp

Related Servers

Alternatives to design-token-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Design system MCP server. 20 tools: extract design tokens from any URL, pull from Figma or Penpot, generate React + shadcn/ui components from specs, run WCAG audits, sync tokens bidirectionally.
      50
      152 npm
      49
      MIT
    • A
      license
      A
      quality
      B
      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
      100 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to work with color: converting between formats like HEX, OKLCH and Display P3, checking and fixing WCAG 2 and APCA contrast, auditing palettes for accessibility and color blindness, and generating palettes, gradients, scales and design tokens.
      18
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive color conversion, manipulation, analysis, and WCAG accessibility tools supporting multiple formats (hex, rgb, hsl, oklch, oklab) for design systems and web development.
      7 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Extract design tokens, colors, typography, spacing and components from any live website, and compute design drift against an approved baseline. Exports DESIGN.md, DTCG, Tailwind and shadcn.
      5,798 npm
      3,878
      MIT

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized into two clear groups: extraction from various sources (CSS, Figma, JSON, Tailwind) and generation/validation for different outputs (CSS, Material3, SwiftUI, Tailwind, contrast validation). Each tool name explicitly indicates its specific source or target, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern throughout. The verbs are clear and descriptive (extract_tokens_from_, generate_, validate_), and the nouns specify the exact format or platform. There are no deviations in naming conventions, making the set highly predictable and readable.

    Tool Count5/5

    With 9 tools, the count is well-scoped for the server's purpose of bridging design tokens across platforms. Each tool earns its place by covering key extraction sources and output formats, providing comprehensive coverage without being overwhelming or redundant.

    Completeness5/5

    The tool surface is complete for the domain of design token conversion and validation. It covers extraction from major sources (CSS, Figma, JSON, Tailwind), generation to key platforms (CSS, Material3, SwiftUI, Tailwind), and includes essential validation (contrast checking). There are no obvious gaps, ensuring agents can handle full workflows without dead ends.

    Maintenance

    ActivityStale
    ResponsivenessSlow