Skip to main content
Glama
m-yoshiro

Storybook MCP Server

by m-yoshiro
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Storybook MCP Server

⚠️ This tool was created for testing purposes and is not recommended for use in production environments.

Getting Started

Before you begin, you need to prepare your Storybook static files. https://storybook.js.org/docs/sharing/publish-storybook

1. Clone the repository

git clone https://github.com/m-yoshiro/storybook-mcp.git
cd storybook-mcp

2. Install dependencies

We recommend using Bun

bun install
# or
npm install

3. Build

bun run build
# or
npm run build

4. Set up

{
  "mcpServers": {
    "storybook-mcp": {
      "command": "node",
      "args": [
        "/< your path>/index.js",
        // Optional: path to your Storybook static json file
        "/< your path>/index.json"
      ]
    }
  }
}

The server will load your Storybook data and expose MCP tools to external agents.

Related MCP server: MCP Boilerplate

🔧 Available Tools

Tool Name

Description

Parameters

list-components

Lists all available components from Storybook

path (optional): Path to the index.json or stories.json file (optional if default path is provided)

find-components-by-name

Finds components based on a keyword (partial match supported)

name: Component name or keyword to search forpath (optional): Path to the index.json or stories.json file (optional if default path is provided)

Available Tools

2 tools
find-components-by-nameC

Search components by name/keyword

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesComponent name or keyword to search for
pathNoPath to the index.json or stories.json file (optional if default path is provided)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the search action without disclosing behavioral traits such as search scope (e.g., partial/full matches), result format, pagination, or error handling. It adds little beyond the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste, clearly front-loading the tool's purpose. It is appropriately sized for a simple search tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a search tool. It lacks details on behavioral aspects like result format, search behavior, or error cases, leaving gaps in understanding how to effectively use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters ('name' and 'path'). The description adds no additional meaning beyond implying 'name' is used for searching, which aligns with the schema. Baseline 3 is appropriate as the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search components by name/keyword' clearly states the action (search) and target resource (components) with a specific criterion (name/keyword). It distinguishes from the sibling 'list-components' by implying filtering rather than enumeration, though not explicitly contrasting them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'list-components' is provided. The description implies usage for searching by name, but lacks context on prerequisites, exclusions, or comparative scenarios, offering minimal direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list-componentsC

Returns all available components

ParametersJSON Schema
NameRequiredDescriptionDefault
pathNoPath to the index.json or stories.json file (optional if default path is provided)

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Returns all available components' implies a read-only operation but doesn't specify whether this is a safe operation, what format the return takes, whether there are rate limits, or any error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just four words. It's front-loaded with the core purpose and contains no wasted words. While it may be under-specified, it's not verbose or poorly structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no annotations, no output schema, and a sibling tool exists, the description is incomplete. It doesn't explain what 'components' are, what 'available' means, how results are returned, or when to use this versus the sibling tool. For a tool that presumably returns data, the lack of output information is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the schema already documents the single optional 'path' parameter. The description adds no parameter information beyond what the schema provides. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic purpose ('Returns all available components') which is clear but vague. It specifies the verb 'Returns' and resource 'components' but doesn't distinguish from the sibling tool 'find-components-by-name' or provide any scope details about what 'available' means. This is adequate but has clear gaps in differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling 'find-components-by-name' tool. There's no mention of alternatives, prerequisites, or context for usage. The agent would have to infer usage patterns from the tool names alone, which is insufficient guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
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

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/m-yoshiro/storybook-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server