What is the Design Token Bridge MCP server?
Design Token Bridge MCP is a local stdio server that translates design tokens between platforms. Its extractors read Tailwind, CSS, Figma variables and W3C DTCG JSON into one schema. Generators then write Material 3 Kotlin, SwiftUI, Tailwind config and CSS variables, and one tool checks WCAG contrast.
Design Token Bridge MCP translates design tokens between platforms. You hand your agent a Tailwind config, CSS custom properties, Figma Variables JSON or a W3C DTCG document, and it gets one universal token schema back. From that schema it can generate native themes.
It was built for a v0 to Figma to coding agent pipeline, and it runs locally over stdio. The repo's stack is TypeScript on Node.js with the MCP SDK and Zod, and it avoids heavyweight build dependencies.
What it changes in your workflow
- Your agent reads tokens from the source you already have instead of retyping colors, spacing and radii by hand.
- One extraction feeds several outputs, so the web, Android and iOS themes start from the same values.
- Contrast is checked against WCAG AA or AAA on color pairs before the theme ships.
- Figma variable aliases and multiple modes are resolved during extraction, and W3C token groups and aliases are parsed too.
How it runs
| Design Token Bridge MCP | |
|---|---|
| Where it runs | On your machine |
| Transport | stdio |
| Install | Global npm package, or build from source |
| Inputs | Tailwind config, CSS custom properties, Figma Variables JSON, W3C DTCG JSON |
| Outputs | Material 3 Kotlin, SwiftUI, Tailwind config, CSS variables |
Who it is for
Best for
- Teams shipping the same brand on web, Android and iOS who want one token source.
- Designers who start in v0 or Figma and need the values turned into code themes.
- Developers who want a quick accessibility check on a color set before release.
Not for
- If your job is mostly pulling a palette and contrast scores out of an image, Color Palette Extractor MCP is the better fit for that.
- When you need design tokens lifted from a live public website, Extract Design System MCP is the better fit for that.
- Go with Standby Design MCP when the task is generating color, type and spacing tokens from scratch rather than converting existing ones.
- Reach for ThemeKit MCP when the job is a token-bound SwiftUI design system with component lookup and Figma variable sync.
Use it with UiChemy
The generated Tailwind config and CSS variables carry your tokens into a web build. For WordPress, UiChemy picks up from there: Figma to WordPress converts a finished design, and Composer is a visual editor inside your WordPress builder. Click Get Started on uichemy.com.
Connect Design Token Bridge MCP: Convert Tokens Across Platforms to your AI client
npm install -g design-token-bridge-mcpInstall the package
Run
npm install -g design-token-bridge-mcp. To build from source instead, clone the repo, then runnpm install && npm run buildinside it.Add the server to your client
For Claude Code, put the config above in ~/.claude/settings.json or in a project .mcp.json. The same stdio entry works in other MCP clients that start a command.
Point at a source build if you built one
If you installed from source, set command to node and args to the path of build/index.js in your clone.
Restart your client
Restart so the nine tools load, then ask the agent to run extract_tokens_from_tailwind on your Tailwind config.
Generate and validate
Pass the extracted tokens to a generator, then run validate_contrast at AA or AAA on the same tokens.
Client configuration
{
"mcpServers": {
"design-token-bridge": {
"type": "stdio",
"command": "npx",
"args": ["-y", "design-token-bridge-mcp"]
}
}
}Endpoints and ports
npx -y design-token-bridge-mcpStarts the server over stdio. Your client normally runs it for you.build/index.jsRun it with node after npm install and npm run build.What you can do with it
- Four token sourcesExtractors cover Tailwind config, CSS custom properties, Figma Variables JSON and W3C DTCG JSON.
- One universal schemaColors, typography, spacing, radii, elevation and motion share a single format that every tool reads and writes.
- Native theme outputGenerators produce Material 3 Kotlin, SwiftUI Swift, a Tailwind config and CSS variables from the same tokens.
- Liquid Glass optionThe SwiftUI generator can add Liquid Glass styling for iOS 26 and later.
- Light and dark CSSThe CSS variables output includes light and dark values switched by prefers-color-scheme.
- WCAG contrast checkOne tool tests color pairs at AA or AAA and reports ratios with pass or fail.
- Alias and mode handlingFigma aliases, multi-mode variables and W3C token aliases are resolved during extraction.
- Free-tier friendlyThe repo documents a setup that works with free tiers of v0 and Figma, plus a manual extraction route when APIs are unavailable.
Tools it exposes
extract_tokens_from_tailwind
Reads Tailwind config content and parses colors, fontSize, spacing, borderRadius and boxShadow.
extract_tokens_from_css
Reads CSS content and extracts the --color-*, --space-*, --radius-* and --shadow-* custom properties.
extract_tokens_from_figma_variables
Parses Figma Variables API JSON, including COLOR and FLOAT types, aliases and multiple modes.
extract_tokens_from_json
Parses W3C DTCG JSON with $value, $type and $description, resolves aliases and handles groups.
generate_material3_theme
Writes Kotlin for Jetpack Compose: lightColorScheme(), Typography and Shapes with Material 3 naming.
generate_swiftui_theme
Writes Swift color extensions and font structs, with optional Liquid Glass for iOS 26 and later.
generate_tailwind_config
Writes a tailwind.config.js theme extend block with rem units, in ESM or CJS form.
generate_css_variables
Writes a :root block of CSS custom properties with light and dark mode through prefers-color-scheme.
validate_contrast
Checks color pairs against WCAG AA or AAA and returns pass or fail with the ratios.
Frequently asked questions
What is Design Token Bridge MCP?
It is an MCP server that converts design tokens between platforms. Extractors read Tailwind, CSS, Figma variables or W3C DTCG JSON into a universal schema, and generators write Material 3, SwiftUI, Tailwind and CSS variable output. A contrast tool checks WCAG levels.
How do I install Design Token Bridge MCP?
Run npm install -g design-token-bridge-mcp, then add an mcpServers entry with command npx and args -y and design-token-bridge-mcp to your client config. You can also clone the repo and build it with npm install and npm run build, then point node at build/index.js.
Which tokens can it read?
It reads Tailwind config content, CSS custom properties such as color, space, radius and shadow variables, Figma Variables API JSON and W3C DTCG JSON. The Figma extractor handles COLOR and FLOAT types, aliases and modes. The W3C extractor resolves aliases and groups.
What can it generate?
It generates Material 3 theme code in Kotlin for Jetpack Compose, SwiftUI colors and fonts with optional Liquid Glass, a Tailwind theme extend block, and a CSS variables block with light and dark modes. Each output starts from the same extracted tokens.
Does it check accessibility?
Yes, in one way. The validate_contrast tool tests color pairs against WCAG AA or AAA and returns pass or fail with the contrast ratios. The repo's example landing page includes a contrast report that passes at the AAA level.
Which AI coding agents work with it?
The README gives Claude Code setup with a stdio entry in settings or a project .mcp.json. The server uses the stdio transport of the MCP SDK, so other MCP clients that can start a command should accept the same entry, though the README documents only Claude Code.
Do I need paid Figma or v0 plans?
No. The repo has setup guides for free tiers of both v0 and Figma, and notes the Figma free tier MCP allowance of six calls per month. A manual token extraction guide covers cases where the API is not available.


