Published 30 August 2026 · Source dated 1 April 2026
A technical write-up on Figma's MCP server shows AI agents faithfully copy whatever inconsistency lives in your components — bad naming, missing Auto Layout, all of it. The wider MCP server ecosystem reportedly grew from ~1,200 servers in Q1 2025 to over 9,400 by April 2026.
The honest bit buried in most MCP hype: agents don't fix messy design systems, they amplify them. If your components have inconsistent naming or missing Auto Layout, Figma's MCP server hands that mess straight to whatever AI agent is generating code from it — garbage in, garbage out, just faster. This is a third-party technical piece, not an official Figma source, so take its specific growth numbers (1,200 to 9,400+ MCP servers) with a pinch of salt. But the direction is real: design system hygiene now has downstream consequences for AI tooling, not just human handoff. If you maintain or contribute to a component library, this is your case for why naming conventions and Auto Layout discipline matter more than ever.
Coach
Pick one component in your library and check its naming and Auto Layout against your design system rules — fix any drift.
Google's Material Design 3 popularised dynamic, token-based theming back in 2021, and it's still what most design-system setups get measured against. If you're building variables in Figma or tokens in Penpot, M3's structure is worth studying, not because it's new, but because it's proven.
open Material 3's token docs and compare their primitive-vs-role token split against your own Figma or Penpot library — note one gap you could fix this week.
Creative Market's 2026 trend forecast flags 'Glasscore' — blur, glow and translucent layers — as a rising visual style. For teams running token-based design systems, that means more theming flexibility, not just flat colour tokens.
Open your team's (or a starter) design system file and check whether blur/elevation tokens exist — if not, sketch one variant using Figma or Penpot's effect styles.
Some teams are wiring AI coding assistants into their design token workflow, using rules and MCP connections to keep components consistent. It's promising but still fragile in practice.
pick one component in your (or a practice) design system and check whether its tokens are named consistently enough that an AI tool could use them without guessing.
