Translate design tokens between Tailwind, Figma, CSS, Material 3, and SwiftUI
This MCP server translates design tokens between Tailwind, Figma, CSS, Material 3, and SwiftUI. It is published as io.github.kenneives/design-token-bridge-mcp under the Model Context Protocol ecosystem, with content tagged for design-tokens, mcp, and related tooling.
π οΈ Key Features
Translate design tokens across Tailwind, Figma, CSS, Material 3, and SwiftUI
Supports MCP server usage within the Model Context Protocol
Project topics include design-tokens, tailwind, figma, css-variables, material-design, and swiftui
π Use Cases
Converting token definitions from one design-system format to another
Bridging workflows between Figma and code (CSS and Tailwind)
Producing equivalents targeting Material 3 and SwiftUI
β‘ Developer Benefits
Standardized integration via MCP
Named repository for design-token-bridge-mcp with documented server identity
β οΈ Limitations
Only translation between the listed platforms is evidenced by available source data
No tool count or specific MCP endpoints are provided in the supplied material
An MCP server that translates design tokens between platforms. Extract tokens from Tailwind, CSS, Figma, or W3C DTCG format β then generate native themes for Material 3 (Kotlin), SwiftUI (with Liquid Glass), Tailwind, and CSS Variables.
Built for the v0 β Figma β Claude Code design pipeline.
Use extract_tokens_from_tailwind with the contents of my tailwind.config.js
2. Generate native themes from the extracted tokens
code
Take those tokens and run them through:
- generate_tailwind_config (for the web app)
- generate_material3_theme (for Android)
- generate_swiftui_theme with liquidGlass=true (for iOS)
- generate_css_variables (for a vanilla CSS fallback)
3. Validate accessibility
code
Run validate_contrast on those tokens at AAA level
Example Output
See the examples/qt-games/ directory for a complete responsive landing page built entirely from MCP-generated tokens, including: