Model Context Protocol explained for designers. How MCP connects AI assistants to your design tools, and why it matters for design systems.
Model Context Protocol (MCP) is an open standard that lets AI assistants talk to external tools. Instead of copy-pasting information between apps, MCP creates a direct bridge.
Without MCP, your AI assistant is blind. It can only see what you paste into the chat. With MCP, it can:
MCP follows a client-server model:
get_design_context, get_variables, etc.Your prompt → AI Assistant (client) → MCP Server → Figma / Tokens / DB ← response ←
| What you ask | What MCP does behind the scenes |
|---|---|
| "Audit my button component" | Calls Figma MCP to read the component, checks tokens, returns findings |
| "What color tokens do we have?" | Calls Tidy MCP to list all variables from your Figma file |
| "Generate a component spec" | Reads the component via MCP, writes a structured spec |
Most MCP servers need a simple JSON config. In Cursor or Claude Code, you add it to your settings:
{ "mcpServers": { "figma": { "url": "http://127.0.0.1:3845/sse" } } }
That's it. The AI assistant discovers available tools automatically.
These newsletter posts go deeper on this topic:
Use AI Design Guide to ship design systems faster.
I'm building the most comprehensive AI design resource. Enter your email and I'll notify you when it's ready.
No spam. Unsubscribe anytime.