A
licenseA
qualityD
maintenanceIntegrates with a running Storybook instance to let AI-powered coding tools browse, inspect, and scaffold components from natural language.
4
MIT
@viantotech/mcp-storybook
Related Servers
Alternatives to @viantotech/mcp-storybook
No user-submitted related servers found.
Related Servers
Storybook MCPofficial
AlicenseNot gradedqualityFmaintenanceEnables AI agents to interact with Storybook by exposing UI component information and development workflows through the Model Context Protocol.271MIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to read and analyze local Storybook component specifications, including component listings, props, and source code examples.3 npmISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, understand, and generate code for design system components by syncing and indexing a component library.-
- AlicenseAqualityBmaintenanceServer that enables AI assistants to interact with Storybook design systems. Extract component HTML, analyze styles, and help with design system adoption and refactoring.9183 npm69MIT
- FlicenseNot gradedqualityDmaintenanceA standalone MCP server that provides AI assistants with comprehensive access to BrowserStack's design system components, enabling component search, detailed prop analysis, and usage examples from Storybook.-
TDQS
B3.3/5.0
Scored across 17 tools
Disambiguation4/5
Most tools have clearly distinct purposes, but the several story retrieval variants (get_story, get_story_metadata, get_story_section, get_story_context) could cause misselection if an agent doesn't read descriptions carefully. Descriptions are detailed enough to resolve most ambiguity.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern (get_, list_, search_, map_, find_, preview_, compare_). There is no mixing of conventions or vague generic verbs.
Tool Count3/5
With 17 tools, the set falls into the 16-25 heavy range. The Storybook domain is broad, but several tools are highly granular and could potentially be consolidated.
Completeness5/5
The tool surface covers the full Storybook workflow: discovering components and stories, retrieving story details and metadata, getting config/usage, previewing, comparing versions, and mapping from Figma/source files. No critical operations appear to be missing.
Maintenance
ActivityMaintained
ResponsivenessNo issues