Design Tokens over MCP: One Change in Figma, Every Screen Follows
Article by PixelA

We changed one colour in Figma and every screen on the site followed. Here is the whole loop, from a Figma variable to a rebuilt Next.js site, and why design and code stop drifting apart.
We changed one colour in Figma. Every screen on the site followed. That's design tokens over MCP, and this is the whole loop.
1. Figma
The colour lives in a variable, not on a hundred layers. Designers change it in one place.
2. MCP
Claude Code reads the variables straight from Figma. No screenshots, no copying hex codes by hand.
3. tokens.css
One line changes. No component is touched, because components only ever refer to the token by name.
4. Next.js
The site rebuilds and every button, tag and toggle picks up the new value.
Why it matters
The design file and the code stop drifting apart, because they read from the same source. A rebrand or a contrast fix becomes a single change instead of a week of hunting through components. It's how we build every design system.
We share one of these breakdowns every week on LinkedIn. Want them in your inbox instead? Subscribe at the bottom of the page.



