Storybook MCPofficial
A
licenseNot graded
qualityF
maintenanceEnables AI agents to interact with Storybook by exposing UI component information and development workflows through the Model Context Protocol.
271
MIT
No user-submitted related servers found.
Scored across 4 tools
Each tool has a distinct purpose: listing components, getting component details, creating components, and composing views from existing components. No overlap or ambiguity.
All tools follow a consistent 'storybook_verb_noun' pattern (list_components, get_component, create_component, compose_view). Convention is uniform and predictable.
With 4 tools, the server covers the essential operations for Storybook without being excessive. The count is well-scoped for its domain.
Core operations are covered: discovery, inspection, creation, and composition. Missing update/delete for components, but these are typically handled via filesystem, not Storybook API.