UCD Coach

daily design digest

AI workflowsAdoption

MCP: the plumbing behind your AI design tools

Published 28 July 2026 · Source dated 28 July 2026

Model Context Protocol (MCP) is the open standard letting AI agents talk to your files, tools and data through one shared interface. It's now baked into Cursor, Claude Code, Zed and Windsurf — not just a Figma thing.

MCP was published by Anthropic in November 2024, but 2026 is when it stopped being niche. An explainer from Decode the Future breaks down the three-part model: **host** (the AI app you use, e.g. Cursor or Claude Code), **client** (the connector), and **server** (the tool being called — your design files, a database, an API). If you've used Figma's MCP server or a coding agent that 'just knows' your component library, this is the plumbing behind it. For a junior designer working across Figma and Penpot, the practical bit is this: agents increasingly pull real design context instead of guessing. Messier files get exposed faster — naming, structure and tokens now double as documentation for a machine, not just your team. Labelling this adoption, not hype — the protocol itself is old news, but the tooling ecosystem around it matured fast this year.

Coach

Pick one Figma or Penpot file you're proud of and tidy its layer names and components as if an AI agent — not just a human — had to read it next.

Source: decodethefuture.org ·