The zeroheight MCP server gives AI tools like Claude, Cursor, and GitHub Copilot direct read access to your design system documentation. Instead of copying and pasting guidelines into every prompt, your AI tool can look them up itself — so the answers it gives, and the code it writes, stay aligned with your design system.
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 tool questions about the design system — which component to use, what the spacing rules are, how to implement a pattern — without leaving their 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. |
Explore the MCP
If you're a zeroheight admin or editor, add the following URL as a custom MCP server in your AI tool:
https://mcp.zeroheight.com/mcp
Your tool will prompt you to authenticate with your zeroheight account.
For Cursor, VS Code, Claude Code, and Codex — admins and editors can find one-click and copy-paste installation commands directly in styleguide settings in the MCP section.
If you're using Figma, ChatGPT/Codex or Claude connect via the respective partner connector.
For all other tools, see their documentation:
Claude Code · VS Code + GitHub Copilot · GitHub Copilot CLI · Windsurf · Zed · JetBrains AI · Gemini CLI · Opencode · Amazon Q · Kiro · Copilot Studio · Bolt · Cursor
To keep your AI tool grounded in your design system as it works, add something like this to your prompts: "Follow the design system guidelines available via the zeroheight MCP". Or learn more about use cases for zeroheight MCP here.
Roll it out to your team
If viewers of your design system documentation in zeroheight access it via SSO, they can use the same details to connect to the MCP using MCP via login. Learn more here.
Otherwise viewers will need to use MCP via link. Learn more here.
FAQ
Can my AI tool access private pages and styleguides via MCP?
It depends on two separate security settings, which behave differently:
Styleguide-level security (the access setting for the styleguide as a whole, e.g. password protection or SSO restriction) has no impact on MCP. A restricted styleguide is just as reachable via MCP as a fully public one — this setting never impacts MCP access.
Page-level privacy (individual pages marked as private) does affect what's reachable, depending on how you've connected:
- MCP via login (authenticating with your zeroheight account, or viewers via SSO): private pages are accessible. Because you're authenticated, your AI tool can read the same content you can.
- MCP via link: private pages are not accessible — only public pages are. Since the link has no authentication, we assume you wouldn't want private content reachable through it.
- Local MCP: private pages are accessible. We assume anyone with your zeroheight API keys is entitled to read private content.