MCP (Model Context Protocol) is an open standard that lets AI tools connect to external data sources. The zeroheight MCP server gives AI assistants like Claude, Cursor, and GitHub Copilot direct read access to your design system documentation — so they can answer questions, reference guidelines, and generate compliant output without you having to copy-paste content manually.
What you can do
Three main workflows benefit from connecting AI tools to zeroheight:
| Workflow | What the MCP enables |
|
Traditional design + handoff Designers work in Figma, developers build in VS Code or Cursor |
Developers and designers can ask their AI coding tool questions about the design system — which component to use, what the spacing rules are, how to implement a pattern — in tools they're already using (ChatGPT, Claude, the editor). |
|
AI-accelerated prototyping PMs and designers using vibe-coding tools like Figma Make |
The AI prototyping tool has direct access to your documented guidelines and components, so generated prototypes stay aligned with the design system from the start. |
|
Full AI-driven development Engineers using AI agents to generate production code |
The coding agent reads your design system documentation as it generates code, so compliance is baked in rather than checked afterwards. |
Remote MCP, zeroheight Figma Make connector and local MCP
Use remote MCP — it's the right choice for most teams. It requires no installation, works with all major AI tools, and lets design system consumers connect their own tools to your styleguide via a unique URL.
Use the Figma Make connector — if you're using Figma Make to generate prototypes.
Use local MCP only if you know you need it. It's intended for teams with specific security requirements, developers who want token-based auth rather than a URL credential. It requires Node.js and API credentials.
If you're not sure which to use, start with remote.
| Remote MCP | Figma Make partner connector | Local MCP | |
| Setup | Enable MCP for your styleguide and paste a URL into your AI tool — no installation | Connect from Figma | Install via npx, configure with API credentials |
| Styleguides | MCP URL per styleguide | All styleguides in the team | All styleguides in the team |
| Auth | Unique per-user, per-styleguide URL (treat as a credential — don't share) | Oauth | API Client ID and Access Token |
| Who can set it up | Anyone with the URL (obtained from an admin or the styleguide) | Only users with a zeroheight editor login | Anyone with a zeroheight login who can generate API keys, or someone who shares their credentials |
| Best for | Designers, developers, and PMs connecting personal AI tools | Design System team members wanting to explore the zeroheight MCP. | Teams with org security policies against remote MCPs, or developer/pipeline use cases |
Get started
- Set up the remote MCP server — for admins enabling access and users connecting their tools
- Set up the local MCP server — for developers who need local setup
- zeroheight connector for Figma Make — for teams using AI-accelerated prototyping in Figma Make
If you want to share MCP access instructions with your team, see: Connect your AI tool to a zeroheight design system.