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
Storybook MCP Server
by m-yoshiro
Related Servers
Alternatives to Storybook MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables AI agents to generate, fetch, and manage UI components through natural language interactions.323 npm7ISC
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server for Storybook.2440 npm46MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to browse Storybook components, manage stories, inspect props, and capture screenshots of components.188 npm14AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.4 npm11MIT
- 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
TDQS
B3/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: 'find-components-by-name' searches for specific components based on a name or keyword, while 'list-components' returns all available components without filtering. There is no overlap or ambiguity between these operations.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern with hyphen-separated words: 'find-components-by-name' and 'list-components'. The naming is predictable and readable throughout the set.
Tool Count2/5
With only 2 tools, the server feels thin for a Storybook domain, which typically involves browsing, testing, and managing UI components. This limited set may not cover common workflows like viewing component details, running tests, or interacting with stories.
Completeness2/5
The tool surface is severely incomplete for a Storybook server. It lacks essential operations such as getting component details, listing or running stories, viewing documentation, or managing component states. Agents will face dead ends when trying to perform basic Storybook tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues