Skip to main content
Glama
kenneives

design-token-bridge-mcp

by kenneives
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to design-token-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • memoire

      memi-design
      A
      license
      A
      quality
      B
      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
      262 npm
      41
      MIT

    • MCP Color Converter

      bennyzen
      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.
      28 npm
      2
      MIT

    • MCP Color Converter

      bennyzen
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive toolkit for color conversion, manipulation, and accessibility analysis supporting formats like OkLCH and WCAG compliance. It enables AI agents to manage design systems by generating harmonious palettes, transforming color spaces, and performing contrast checks.
      2
      MIT

    • huetension mcp

      leporel
      A
      license
      Not graded
      quality
      B
      maintenance
      Extract palettes from images, generate harmonies, gradients, random palettes; Check WCAG and APCA contrast; Suggest nearest passing OkLCH lightness; Simulate color-blindness; Convert and sort colors across formats (hex / RGB / HSL / OkLCH / …)
      MIT

    • ds-mcp-sync

      blumaa
      F
      license
      A
      quality
      D
      maintenance
      Syncs design tokens and components from Figma to a Design System codebase, enabling automated generation of React components and Storybook stories.
      5
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessSlow

    Resources