A public component library your assistant can look things up in.
Before writing UI code, your assistant can see which components a team's public Storybook offers and read how each one is meant to be used, so it builds with the design system instead of around it.
What it is
A community-built server that runs on Apify and turns a publicly available Storybook into something your assistant can read. Storybook is where teams document UI components, with examples, props and code samples. This is not Storybook's own MCP addon; its developer, Eva Baldasseroni, built it because that addon was hard to deploy outside local development.
What you get
- Every component in the Storybook, listed once
- A component's docs page as ordered Markdown: headings, text, lists, code blocks and the props table
- Links to a component's stories and docs pages
- Guidance for assembling UI from the library, with your own extra instructions appended if you set them
Requirements
An Apify account and your own Apify API token, from Settings > API & Integrations in Apify Console; the server refuses any request that does not carry it. You pay per tool call plus Apify platform usage; the per-call prices are on the Actor's pricing tab. You set the public address of the Storybook you want to read in the Actor's input, ending in a slash. Custom blocks on a docs page come back as plain text only.
Setup effort
Paste a URL with a key — add the endpoint to your client