Skip to main content

Set up the local MCP server

Tom Daly
Tom Daly
  • Updated
Available on all plans. Free and Starter are limited to 500 calls per month. Search requires an Enterprise plan with AI features enabled. Upgrade for higher limits and other premium features.

Most teams should use the remote MCP server — it requires no installation and works with all major AI tools. Use the local MCP server if your organization restricts remote MCP connections.

To connect from a CI/CD pipeline, use API credentials with Access via login instead.

Not sure which to use? Read the zeroheight MCP overview.

What you'll need

Before you start:

  • Node.js version 22 or higher
  • A zeroheight account with at least one styleguide
  • Optional: your zeroheight Client ID and Access Token, if you don't want to sign in through your browser
  • A tool that can connect to MCP servers.

Sign in or use API credentials

By default, the local MCP server opens your browser the first time it connects, so you can sign in to zeroheight. This works the same way as Access via login: admins and editors can create and edit pages, and viewers who sign in via SSO can read.

To sign in, leave out the ZEROHEIGHT_ACCESS_TOKEN and ZEROHEIGHT_CLIENT_ID environment variables in the setup examples below. To use API credentials instead, include them.

Connections that use API credentials are read only, even if the API token has write scopes. The Access via login settings for your organization and for each styleguide don't apply to them. They reach every styleguide the API token can access.

Get your API credentials

Skip this step if you're signing in through your browser. Only Enterprise teams can create API tokens with the scopes the MCP needs.

  1. Open your zeroheight account settings
  2. Navigate to the API section
  3. Generate a Client ID (starts with zhci_) and Access Token (starts with zhat_)

If you need help creating API credentials, see the API authentication guide.

Setup

Claude Desktop

  1. Download and install Claude Desktop
  2. Open Claude Desktop settings
  3. Go to the Developer tab
  4. Click "Edit Config"
  5. Add this configuration:
{
  "mcpServers": {
    "zeroheight": {
      "command": "npx",
      "args": ["-y", "@zeroheight/mcp-server@latest"],
      "env": {
        "ZEROHEIGHT_ACCESS_TOKEN": "zhat_abc123",
        "ZEROHEIGHT_CLIENT_ID": "zhci_abc123"
      }
    }
  }
}

Replace the example tokens with your actual credentials.

  1. Restart Claude Desktop
  2. Look for the MCP indicator in the chat interface

VS Code with GitHub Copilot

  1. Create .vscode/mcp.json in your workspace:
{
  "inputs": [
    {
      "type": "promptString",
      "id": "zeroheight-token",
      "description": "Zeroheight Access Token",
      "password": true
    },
    {
      "type": "promptString", 
      "id": "zeroheight-client",
      "description": "Zeroheight Client ID",
      "password": true
    }
  ],
  "servers": {
    "zeroheight": {
      "command": "npx",
      "args": ["-y", "@zeroheight/mcp-server@latest"],
      "env": {
        "ZEROHEIGHT_ACCESS_TOKEN": "${input:zeroheight-token}",
        "ZEROHEIGHT_CLIENT_ID": "${input:zeroheight-client}"
      }
    }
  }
}
  1. Open Command Palette (⇧⌘P on macOS, F1 on Windows) and run MCP: Add Server
  2. Enter your credentials when prompted
  3. Enable Agent Mode in GitHub Copilot Chat

Cursor IDE

  1. Open Settings → MCP Servers
  2. Click "Create New MCP Server"
  3. Configure:
    • Name: zeroheight
    • Command: npx
    • Args: ["-y", "@zeroheight/mcp-server@latest"]
    • Environment variables:
      • ZEROHEIGHT_ACCESS_TOKEN: your token
      • ZEROHEIGHT_CLIENT_ID: your client ID
  4. Save and restart Cursor

What you can do with the MCP

Once connected, the local MCP server provides the same read tools as the remote server. See the zeroheight MCP tools reference for full details. The write tools are available to admins and editors who sign in, not to connections that use API credentials.

Troubleshooting

Server not appearing after setup?

  1. Check Node.js version: node --version (needs 22+)
  2. If you use API credentials, verify they're correct
  3. Check JSON syntax in config file
  4. Restart your client completely

"There are no accessible styleguides..." error?

  1. If you use API credentials, confirm your access token and client ID
  2. Make sure your account has styleguide access
  3. If you use API credentials, check whether they've expired

Server won't start?

  1. Test manually: npx @zeroheight/mcp-server@latest
  2. Check internet connection
  3. Look for firewall issues

For more help, contact support@zeroheight.com or check the help center.

Share this article
Was this article helpful?