MCP server

Design Token Bridge MCP: Convert Tokens Across Platforms

The Design Token Bridge MCP server extracts tokens from Tailwind, CSS, Figma variables or W3C JSON and generates Material 3, SwiftUI, Tailwind and CSS variable themes.

Run
npm install -g design-token-bridge-mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

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 runsOn your machine
Transportstdio
InstallGlobal npm package, or build from source
InputsTailwind config, CSS custom properties, Figma Variables JSON, W3C DTCG JSON
OutputsMaterial 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.