Lets AI agents scaffold modern npm packages, CLIs, HTTP services, and apps as a native tool. Three tools: inspect the full option/preset schema, preview the generated file tree for a config, and write the project to disk.
3
361
1
MIT
Why this server?
Auto-syncs token and component changes to Storybook documentation, ensuring design system docs stay up-to-date without manual rebuilding.
Enables AI agents to access design system tokens and component contracts through MCP, reducing token usage and ensuring consistency.
29
MIT
Why this server?
Provides an MCP server that integrates with Storybook, allowing AI tools to query available UI components, retrieve component information and usage examples to help implement UI from design specifications.
A Model Context Protocol server that integrates with Storybook to help AI tools query UI components and retrieve usage examples from static Storybook files.
2
486
21
MIT
Why this server?
Provides access to Storybook example code for Salt Design System components to help agents generate accurate UI code.
Enables AI agents to build React applications using JP Morgan Chase's Salt Design System by providing real-time access to component APIs, documentation, and accessibility guidelines. It supports tasks such as scaffolding new projects, building UI patterns, and converting Figma designs into Salt code via the Model Context Protocol.
6
14
1
MIT
Why this server?
Allows browsing, inspecting, creating, and composing components in a running Storybook instance.
Integrates with a running Storybook instance to let AI-powered coding tools browse, inspect, and scaffold components from natural language.
4
MIT
Why this server?
Extracts component information from Storybook design systems, including HTML, styles, component metadata, props documentation, theme information, and relationships between components.
Server that enables AI assistants to interact with Storybook design systems. Extract component HTML, analyze styles, and help with design system adoption and refactoring.
9
103
69
MIT
Why this server?
Scans Storybook documentation to extract component information and props, reconciles conflicts with other sources, and includes them in the authoritative design contract.
Design contract layer for AI agents. Scans Figma, code, Storybook, and token files, reconciles conflicts, and serves a single machine-readable source of truth so every agent gets the same authoritative design rules before it builds. Local-first.
6
823
18
Apache 2.0
Why this server?
Planned integration to auto-generate Storybook stories for existing components.
9 MCP servers for React + TypeScript development automation — component scaffolding, dependency auditing, WCAG accessibility checking, test generation, TypeScript enforcement, and monorepo management. 134 tests, CI on Node 20+22.
7
65
3
MIT
Why this server?
Provides tools for extracting component lists, props information, and custom data from Storybook documentation, enabling AI to understand and reference UI component libraries.
