The zeroheight MCP exposes two sets of tools:

• Read tools are for providing context from zeroheight to agent tasks where the output will increase in quality due to zeroheight context
• Write tools are for providing agents the capability to write content into zeroheight. Only available to admins/editors who connect using MCP via Login. Currently in closed beta — learn more.

AI agents call these automatically as they work through your prompt — you don't invoke them directly.

Read tools

list-styleguides

Discovers all zeroheight styleguides accessible via the connected MCP. Returns a list of styleguide IDs and names. This is typically the first call an agent makes.

Not called when using MCP via Link — the connection is already scoped to a single styleguide.

search-pages

Searches the styleguide for pages matching a keyword or topic and returns a list of relevant chunks from the styleguide. The agent will likely use this tool first and may fetch further content if the chunks are insufficient. 

Search results don't include a way to access relevant images; agents will follow up with get-page and get-page-asset if needed. It's possible to search a specific release of a styleguide.

Note: only available for teams on an Enterprise plan who have enabled AI features in zeroheight. Learn how to enable AI features here and update your plan here.

list-pages

Returns the full navigation tree for a styleguide — sections, categories, pages, and tabs. The agent may this to identify which pages are relevant before fetching content. It's possible to list the pages of a specific release of a styleguide.

get-page

Fetches the content of a specific page as Markdown, including usage notes, guidance, and any embedded assets. This is the source of truth for what the agent uses when applying your design system. It's possible to get the page from a specific release.

get-page-asset

Fetches images or file attachments referenced in a get-page response. Accepts multiple URIs in a single call.

How well an agent can use a fetched asset depends on the file type and the agent:

• Images are the most reliably supported — they come back in a format agents can view and reason about directly.
• Non-image files (PDFs, Word, Excel, ZIP) are inconsistent. Some agents can't process the content at all; others recognise the file type and skip the tool rather than attempt it. Agents with code execution (e.g. Claude Code) can sometimes unpack and read these files, but this isn't guaranteed across tools.

When an asset can't be fetched or parsed, the tool returns the asset's source URL so the agent can pass it on for direct download. This means content added to a styleguide as a non-image attachment may not be readable by every agent via MCP, even though it remains accessible on the web.

list-releases

Lists available releases for a styleguide. Only called when the user explicitly requests content from a specific release.

How the tools work together

A typical agent session follows this sequence (assuming zeroheight team has enabled AI features):

1. list-styleguides — identify available styleguides (skipped when using Access via link)
2. search-pages — identify relevant chunks of the styleguide and the IDs of the pages that contain them
3. get-page — (optional) fetch the content of relevant pages if the chunks are insufficient or the agent needs images/attachments
4. get-page-asset — (optional) fetch any images or attachments referenced in those pages
5. list-page — (optional) list the full navigation tree in case the agent wants to identify relevant pages that weren't returned by search-pages

Without AI features enabled or on the Free/Starter plan, the sequence is:

1. list-styleguides — identify available styleguides (skipped when using Access via link)
2. list-pages — identify relevant pages of the styleguide
3. get-page — fetch the content of relevant page
4. get-page-asset — (optional) fetch any images or attachments referenced in those pages

list-releases is only used when versioned content is requested, after which list-pages and get-page are called with the relevant releaseId.

Write tools

Only available for admins and editors who connect to using MCP via login.

get-page

While this tool is available list as a read tool, it gains a format property when writing is available. It defaults to the reading format but the agent typically asks for the editor format when in appropriate contexts, for example to reuse a canonical page as the basis for a new one. The editor format always reads the current page, so it can't be combined with a release ID.

create-page

Creates a page in a category, with content and an optional hidden flag. Returns the page's ID, URL and version.

edit-page

Applies ordered find/replace changes to an existing page's content. always save to a draft, so the latest/work in progress page is never changed until someone merges the draft via the UI. Learn more about drafts here.

upload-asset

Uploads an image or a downloadable attachment and returns the path page content must use to reference it.

list-design-libraries

Lists the design libraries whose designs can be placed on a page, and reports whether Figma is still connected.

get-designs

Lists one library's designs, filterable by source node ID, kind or name, so the agent can reference an exact frame or component.

list-component-sets / get-component-set

Finds component sets and the component and field IDs a component-set block accepts.

list-token-sets / list-tokens

Lists token sets and their tokens, for token mentions and token management blocks.

list-repositories / get-repository / create-markdown-snapshot

Finds connected repositories, lists the markdown files in the last-synced tree, and snapshots one file for embedding. A repository that has never synced can't be read — only a person can sync it in zeroheight.

get-storybooks / get-stories

Lists Storybook links and their stories. VPN-restricted Storybooks can't be reached.

get-livecode-settings

Returns the npm packages and shared resources a styleguide's livecode previews run against.

read-resource

Reads this server's MCP resources — the editor XML guide and livecode templates — for clients that can't read resources directly.