Skip to main content

Set up MCP Access via link

Rab Rennie
Rab Rennie
  • Updated
This feature is not available for Free or Starter plans. Want this and other premium features? Update your plan here.

This article covers setting up MCP via Link — the only way for viewers to connect their AI tools to your zeroheight styleguide. If you're a zeroheight admin or editor looking to connect your own AI tool, use MCP via Login instead — see the zeroheight MCP overview.

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

Enabling  MCP via Link for a styleguide

Styleguides created before 4th March 2026 have remote MCP disabled by default. Styleguides created after that date have it enabled by default.

  1. Head to your styleguide settings
  2. In the sidebar on the left select MCP
  3. Under Remote MCP access toggle Enable remote MCP access on

Share access with your team

Once enabled, add a Remote MCP details block to a page in your styleguide. This generates each viewer's unique URL automatically — they'll see their own URL, not yours.

  1. Open the slash inserter on any page and select Remote MCP details
  2. Configure which client tabs are visible using the block's settings panel
  3. Optionally turn off Display help message if you're providing your own setup guidance

The block includes setup instructions for Cursor, VS Code, Claude Code, and Codex. For other tools, viewers can use the Raw URL tab and their tool's own documentation.

Note: each viewer's URL is unique to them — don't share your own URL directly.

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.

Share this article
Was this article helpful?