
Design Token Bridge Mcp
io.github.kenneivesPublished by GitHub account kenneivesv1.0.2Updated Oct 24, 2026
Translate design tokens between Tailwind, Figma, CSS, Material 3, and SwiftUI
Overview
Local MCP server that converts design tokens between Tailwind, CSS, Figma variables, W3C DTCG JSON, Material 3 and SwiftUI themes.
- What you can do
- Extract tokens from Tailwind config, CSS custom properties, Figma Variables JSON and W3C DTCG JSON into one universal token schema
- Generate a Material 3 Kotlin theme, a SwiftUI theme (optionally with Liquid Glass), a Tailwind config, or CSS variables with light/dark mode
- Check color pairs for WCAG AA/AAA contrast and return pass/fail with ratios
- Chain the steps so one source of tokens can be pushed out to web, Android and iOS targets
- When to use it
- Useful when a design system or brand palette has to be carried across web, Android and iOS codebases, or when you want an assistant to regenerate native theme files and check contrast from an existing Tailwind, CSS or Figma token source.
- Requirements
- Runs as a local stdio process on the desktop. Install the npm package globally or run it with npx, or build it from source with Node.js and run the built entry file. No accounts, API keys or environment variables are declared; token inputs are passed as file contents.
Installation
In SourceWeft
- Open Design Token Bridge Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[AgentAvow Trust] — signed, offline-verifiable tool-safety grade
design-token-bridge-mcp
[Image][AgentGraph Trust Score]
Verified on AgentGraph — trust infrastructure for AI agents. View profile
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.
Install
From npm
From source
Configure with Claude Code
Add to your Claude Code MCP settings (~/.claude/settings.json or project .mcp.json):
Or if installed from source:
Tools (9 total)
Extractors — Input → Universal Tokens
Generators — Universal Tokens → Output
Validation
Universal Token Schema
All tools speak this common format:
Example: Full Pipeline
1. Extract tokens from a Tailwind config
2. Generate native themes from the extracted tokens
3. Validate accessibility
Example Output
See the examples/qt-games/ directory for a complete responsive landing page built entirely from MCP-generated tokens, including:
qt-games-tokens.json— extracted universal tokenstailwind.config.js— generated Tailwind configvariables.css— generated CSS custom propertiescontrast-report.json— WCAG validation (AAA pass)index.html+styles.css— responsive landing page using the generated tokens
v0 + Figma Free Tier Setup
This MCP works with free tiers of both v0 and Figma. See the setup guides:
- v0 Setup Guide — free tier signup, web UI workflow
- Figma Setup Guide — free tier MCP config (6 calls/month)
- Claude Code Setup — full pipeline configuration
- Token Extraction Guide — manual extraction when APIs aren't available
Tech Stack
- TypeScript + Node.js
- @modelcontextprotocol/sdk v1.x (stdio transport)
- Zod for schema validation
- Zero heavyweight dependencies — no Babel, no PostCSS, no Style Dictionary
Tests
Contributing
See CONTRIBUTING.md for development setup, project structure, and PR guidelines.
License
MIT — see LICENSE.
Source: README.md at commit d13c8b3
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts