design-token-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_tokens_from_tailwindC | Parse a Tailwind config and extract theme values into universal design tokens |
| extract_tokens_from_cssA | Parse CSS custom properties (variables) and extract design tokens |
| extract_tokens_from_figma_variablesB | Parse Figma variables export JSON and extract design tokens |
| extract_tokens_from_jsonA | Parse W3C Design Tokens Community Group (DTCG) format JSON into universal tokens |
| generate_material3_themeC | Generate Kotlin Jetpack Compose Material 3 theme files from universal design tokens |
| generate_swiftui_themeC | Generate SwiftUI theme files from universal design tokens, with optional Liquid Glass support |
| generate_tailwind_configB | Generate a tailwind.config.js theme from universal design tokens |
| generate_css_variablesC | Generate CSS custom properties from universal design tokens with light/dark mode support |
| validate_contrastB | Check color combinations in design tokens for WCAG AA/AAA accessibility compliance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.