Storybook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-componentsC | Returns all available components |
| find-components-by-nameC | Search components by name/keyword |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.