MCP server

Design System Extractor MCP: Read Storybook Components

The Design System Extractor MCP server connects an AI coding agent to a Storybook instance, so it can list components, extract rendered HTML and read theme tokens.

Run
claude mcp add design-system npx mcp-design-system-extractor@latest --env STORYBOOK_URL=http://localhost:6006
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the Design System Extractor MCP server?

The Design System Extractor MCP server reads a Storybook design system for an AI coding agent. It lists and searches components, extracts rendered HTML and styles, maps component dependencies and pulls theme tokens such as colors, spacing and typography. You point it at your Storybook with the STORYBOOK_URL variable.

The Design System Extractor MCP server connects to a Storybook instance and extracts component information for an AI coding agent. It reads rendered HTML, styles and component metadata, and it works with built Storybook distributions.

A headless Chrome session through Puppeteer renders dynamic JavaScript components. The server runs on your machine, and the STORYBOOK_URL variable points it at your Storybook, with the local port 6006 as the default.

What it changes in your workflow

  • Your agent lists and searches components by name, title, category or purpose, such as form inputs, navigation, feedback and buttons.
  • It reads the rendered HTML of a story and its variants, so new code can match markup that already exists.
  • It analyzes rendered HTML to find which other components a component uses, including React components, web components and CSS class patterns.
  • It extracts theme information such as colors, spacing, typography, breakpoints and CSS custom properties.
  • Long operations run as background jobs that the agent can poll, cancel and list.

Setup at a glance

Design System Extractor MCP server
Where it runsOn your machine, started with npx
NeedsA Storybook instance, plus Chrome or Chromium for Puppeteer
Main settingSTORYBOOK_URL, which points at your Storybook
Self-signed certificatesSet NODE_TLS_REJECT_UNAUTHORIZED to 0

Who it is for

Best for

  • Teams with a Storybook who want agents to reuse the components they already have.
  • Developers refactoring a codebase toward a design system and needing rendered HTML as a reference.
  • Anyone who needs colors, spacing and typography tokens from a Storybook theme and its CSS.

Not for

  • If you need to generate or update Storybook stories from your own design system components, Story UI MCP Server is the better fit for that.
  • When the job is reading design tokens from any live URL instead of a Storybook, the designlang MCP server is the better fit for that.
  • If your job is extracting real colors, typography and spacing from a live site, the Extract Design skill is the better fit for that.
  • When the job is checking extracted design tokens for drift, Dembrandt MCP Server is the better fit for that.