This article covers setting up MCP via link. If you're a zeroheight admin/editor or viewers of your design system documentation access it via SSO, we recommend using MCP via login instead — see the zeroheight MCP overview.

If viewers of your design system don't access it via SSO, they can use MCP via link. With MCP via link, it's recommended that each viewer connects to the MCP via link using their own unique URL. Further details below.

Watch a full walkthrough — from getting your URL to connecting your tools and demoing live use cases:

Enabling  MCP via link

Go to  Your organization → Integrations and click Edit MCP settings under Model Context Protocol (MCP).

If MCP via link is enabled for your team, you can choose which styleguides are accessible can be accessed using MCP via link.

Styleguides created before 4th March 2026 have remote MCP disabled by default. Styleguides created after that date have it enabled by default. If you want to change this setting for a styleguide:

1. Head to styleguide settings
2. In the sidebar on the left select MCP access
3. And select the MCP via link tab

Share access with your team

Add a Remote MCP details block to a page in your styleguide so that viewers are able to get their unique MCP URL.

1. Open the slash inserter on any page, select Remote MCP details and select MCP via link
2. Optionally configure which client tabs are visible using the block's settings

3. 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.

Connect the MCP to your AI tool

For Cursor, VS Code, Claude Code, and Codex — use one-click and copy-paste installation commands directly in the block.

For all other tools, see their documentation:

Claude · VS Code + GitHub Copilot · GitHub Copilot CLI · Windsurf · Zed · JetBrains AI · Gemini CLI · Codex · Opencode · Amazon Q · Kiro · Copilot Studio · ChatGPT · Bolt

Connecting to multiple styleguides

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 remote MCP

Disabling remote MCP access:

• Removes the Remote MCP details block from the viewer-facing release
• Removes the remote MCP 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 current MCP sessions to permanently invalidate all existing MCP URLs. Remote MCP stays enabled, but anyone who needs access must fetch a new URL.