This article covers setting up Access via link. If you're a zeroheight admin/editor, or viewers of your design system sign in via SSO, we recommend Access via login instead — see Set up MCP access via login. Not sure which to use? Start with the zeroheight MCP overview.
If viewers of your design system can't sign in via SSO, they can use Access via link. Each viewer gets their own unique MCP URL per styleguide. No sign-in is needed, so anyone with a URL can connect — which is why each viewer should use their own URL rather than a shared one. Access via link is read only: private pages aren't reachable and the write tools aren't available.
Watch a full walkthrough — from getting your URL to connecting your tools and demoing live use cases:
Enabling Access via link
Go to Your organization → MCP (or use the zeroheight MCP shortcut in your profile menu) and turn on Access via link under Enable MCP.
Once Access via link is enabled for your organization, the MCP styleguide access table shows which styleguides can be reached this way. Click Edit next to a styleguide to change it.
Styleguides created before 4th March 2026 have Access via link disabled by default. Styleguides created after that date have it enabled by default. To change this setting from within a styleguide:
- Head to styleguide settings
- In the sidebar on the left select MCP
- Select the Access via link tab and toggle Enable MCP – Access via link
Share access with your team
Add a remote MCP details block to a page in your styleguide so that viewers can get their unique MCP URL.
- Open the slash inserter on any page, select Remote MCP details and select Access via link
- Optionally configure which client tabs are visible using the block's settings
-
Optionally turn off Display help message if you're providing your own setup guidance
Note: each viewer's URL is unique to them — don't share your own URL directly. Your own URL is shown under Styleguide settings → MCP → Access via link.
Connect the MCP to your AI tool
The remote MCP details block gives each viewer their unique URL, along with one-click and copy-paste install options for Cursor, VS Code, Claude Code, Codex and Kiro. Add the URL as a custom MCP server in your AI tool — no sign-in is needed.
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
Connecting to multiple styleguides
Each Access via link URL is scoped to one styleguide. Add each styleguide as a separate MCP server with a distinct name. Disable the ones you're not using in your client, or specify which one to use in your prompts.
Manage access
Disable Access via link
Turning off Access via link for a styleguide (or for your whole organization):
- Removes the Remote MCP details block from the viewer-facing release
- Removes the Access via link URL from styleguide settings and the editor view of the block
- Immediately stops all existing MCP URLs from returning data
Re-enabling it later will restore access for previously generated URLs.
Revoke all URLs without disabling
Use Disconnect all MCP sessions on the Access via link tab to permanently invalidate all existing MCP URLs for that styleguide. Access via link stays enabled, but anyone who needs access must fetch a new URL.