The zeroheight MCP server connects AI tools like Claude, Cursor, Figma Make and GitHub Copilot to your design system. Your AI tool can read your documentation, components and tokens as it works — so the answers it gives, and the code it writes, stay aligned with your design system without you pasting guidelines into every prompt.
It works in both directions. With MCP write, admins and editors can also have their agent create and edit pages in zeroheight, using the context it already has from your codebase, Figma files and other tools.
What you can do
Four 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. |
|
Maintaining documentation Admins and editors using agents to create and update pages |
With MCP write, an agent can draft a new page from your codebase or Figma files, make targeted edits to an existing page, work through review comments and merge drafts — all from the conversation. Learn more about writing to zeroheight via MCP. |
Coding agents can also check the style values in your code against your design tokens and swap in the right token where it's safe. Learn more about token linting.
Ways to connect
There are three ways to connect an AI tool to zeroheight. Which one to use depends on who's connecting and how they sign in to zeroheight.
| Access via login | Access via link | Local MCP server | |
|---|---|---|---|
| Who it's for | Admins and editors, and viewers who sign in to zeroheight via SSO | Viewers who can't sign in via SSO | Teams whose organization restricts remote MCP connections, or who run the MCP in a CI/CD pipeline |
| How you connect | Sign in to zeroheight from your AI tool, with your username and password or via SSO | A unique URL per person, per styleguide. No sign-in needed, so anyone with the URL can connect | Runs on your machine using your zeroheight API Client ID and Access Token |
| Private pages | Accessible | Not accessible | Accessible |
| Write access | Admins and editors, when MCP write is enabled | Read only | Read only |
| Setup guide | Set up MCP access via login | Set up MCP access via link | Set up the local MCP server |
Admins control which methods are enabled for the organization under Your organization → MCP (or the zeroheight MCP shortcut in your profile menu), and which styleguides each method can reach under Styleguide settings → MCP.
Get started
If you're a zeroheight admin or editor, the quickest way to try the MCP is Access via login. Add the following URL as a custom MCP server in your AI tool:
https://mcp.zeroheight.com/mcp
Your tool will prompt you to sign in with your zeroheight account.
For Cursor, VS Code, Claude Code, Codex and Kiro, you can find one-click and copy-paste installation commands under Styleguide settings → MCP.
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 sign in to zeroheight via SSO, they can use the same sign-in to connect with Access via login. Set up MCP access via login.
Otherwise, viewers can connect with Access via link, where each person gets their own unique URL and no sign-in is needed. Set up MCP access via link.
In both cases, add the remote MCP details block to a page in your styleguide so viewers can pick up their connection details, and one-click install commands for popular tools, without leaving the styleguide.
Guides
- Set up MCP access via login — for admins, editors and SSO viewers
- Set up MCP access via link — for viewers who can't sign in via SSO
- Set up the local MCP server — for restricted networks and CI/CD
- Writing to zeroheight via MCP — create and edit pages with an agent
- Token linting — check code against your design tokens
- zeroheight MCP tools reference — every read and write tool, and how agents use them
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:
- Access 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.
- Access 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 server: private pages are accessible. We assume anyone with your zeroheight API keys is entitled to read private content.
Can my AI tool create or edit pages in zeroheight?
Yes, if you're an admin or editor connected via Access via login. MCP write is on by default; a team admin can turn it off under Your organization → MCP. Viewers, and anyone connected via Access via link or the local MCP server, get the read tools only.
On Professional and Enterprise, new pages and edits go into a draft unless you explicitly ask your agent to publish directly. On Free and Starter, where drafts aren't available, changes go straight to the published page and count towards the monthly call limit. Learn more about writing to zeroheight via MCP.