storybook-mcp-integration — Claude Code skill: features and install
The storybook-mcp-integration Claude Code skill connects Storybook MCP tools to work with existing components. The agent can find component docs, open story previews, and run story tests.
MIT 166 installs ★ 305 updated 2026-11-14
npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a claude-codeWhat storybook-mcp-integration does
The skill lets an agent inspect a project's component library through Storybook MCP. It can retrieve component props and story source, browse documentation, show previews, and run story tests with accessibility checks. The agent can inspect existing stories before creating a component.
It requires Storybook 10.3+ with the Vite builder and the @storybook/addon-mcp package; testing tools also need @storybook/addon-vitest. Component discovery through documentation requires componentsManifest in .storybook/main.ts. Register the MCP server in Claude Code with npx mcp-add --type http --url "http://localhost:6006/mcp" --scope project. For building components from mockups, the related skill is design-to-code.
What it helps with
- find existing components and inspect their props
- retrieve component documentation and story source
- open a preview of a component story
- run story tests with accessibility checks
Example prompts for the agent
- Find existing button components in Storybook and show their props.
- Open a preview of the
Button/Primarystory. - Run story tests with accessibility checks for the new components.
How to install storybook-mcp-integration
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a claude-code2Manually: put the files in place
~/.claude/skills/storybook-mcp-integration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/storybook-mcp-integration/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a codex2Manually: put the files in place
.agents/skills/storybook-mcp-integration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a cursor2Manually: put the files in place
.cursor/skills/storybook-mcp-integration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yonatangross/orchestkit src/skills/storybook-mcp-integration2Manually: put the files in place
.github/skills/storybook-mcp-integration/SKILL.md1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a gemini-cli2Platform CLI
gemini skills install https://github.com/yonatangross/orchestkit --path src/skills/storybook-mcp-integrationManually: put the files in place
.devin/skills/storybook-mcp-integration/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about storybook-mcp-integration
How do I install storybook-mcp-integration in Claude Code?
Run npx skills add yonatangross/orchestkit --skill storybook-mcp-integration -a claude-code. The skill file is placed at ~/.claude/skills/storybook-mcp-integration/SKILL.md.
What does storybook-mcp-integration do?
It gives the agent access to Storybook MCP tools for finding components and docs, previewing stories, and running tests. The skill is for working with components that already exist in the project.
What does storybook-mcp-integration need to run?
It needs Storybook 10.3+ with the Vite builder and @storybook/addon-mcp. Story tests through MCP require @storybook/addon-vitest, while documentation discovery requires componentsManifest in .storybook/main.ts.
Source text
SKILL.md · MIT
---
name: storybook-mcp-integration
license: MIT
compatibility: "Claude Code 2.1.277+. Optional: @storybook/addon-mcp (Storybook 10.3+, Vite-based only)."
description: "Storybook MCP server (@storybook/addon-mcp) tools and toolsets. Use when calling them on existing components. To build from a mockup, use design-to-code."
user-invocable: false
disable-model-invocation: false
targets:
- library: storybook
version: ">=10.6.1"
metadata:
category: document-asset-creation
mcp-server: storybook-mcp
version: "1.0.0"
author: "OrchestKit"
complexity: "medium"
tags: "storybook, mcp, component-discovery, story-preview, component-testing, a11y, design-system, react"
allowed-tools: "Read Glob Grep WebFetch WebSearch ToolSearch mcp__storybook-mcp__get-storybook-story-instructions mcp__storybook-mcp__preview-stories mcp__storybook-mcp__list-all-documentation mcp__storybook-mcp__get-documentation mcp__storybook-mcp__get-documentation-for-story mcp__storybook-mcp__run-story-tests"
paths:
- ".storybook/**"
- "src/**/*.stories.{ts,tsx}"
---
# Storybook MCP Integration
Use the Storybook MCP server (`@storybook/addon-mcp`) to give agents awareness of a project's actual component library — props, stories, tests, and live previews.
## When to Use
- **Component generation** — check existing Storybook components before creating new ones
- **Component testing** — run story tests + a11y audits via MCP instead of CLI
- **Visual verification** — embed story previews in chat for user confirmation
- **Component auditing** — inventory components with full metadata via MCP
## Quick Reference — 6 Tools, 3 Toolsets
| Toolset | Tool | Purpose | Key Inputs |
|---------|------|---------|------------|
| **dev** | `get-storybook-story-instructions` | Guidance on writing stories + interaction tests | none |
| **dev** | `preview-stories` | Returns preview URLs for stories (embeddable) | `stories[]: {storyId}` or `{absoluteStoryPath, exportName}` |
| **docs** | `list-all-documentation` | Full component + docs manifest index | none |
| **docs** | `get-documentation` | Props, first 3 stories, story index, docs | `id` (required), `storybookId` (optional) |
| **docs** | `get-documentation-for-story` | Full story source + component docs | `componentId`, `storyName` (required) |
| **testing** | `run-story-tests` | Run component + a11y tests, pass/fail + violations | `stories[]` (optional), `a11y` boolean (default true) |
## Prerequisites
```bash
# Storybook 10.3+ with Vite builder (no webpack)
npx storybook@latest upgrade
# Install the addon (current: @storybook/[email protected], Apr 2026)
npx storybook add @storybook/addon-mcp
# Enable docs toolset (required for component discovery)
# In .storybook/main.ts:
# componentsManifest: true
# NOTE: the old `experimentalComponentsManifest` flag was renamed in
# Storybook 10.3; it is now `componentsManifest` and default-on. Any
# code still passing the `experimental` prefix will warn-then-ignore.
# For Chromatic remote setups, use the standalone package instead of
# the addon (same tool surface, no local Storybook required):
# npm i -D @storybook/mcp
# npx storybook-mcp --registry https://chromatic.storybook.cloud
# Enable testing toolset (requires addon-vitest)
# npx storybook add @storybook/addon-vitest
# Register with Claude Code
npx mcp-add --type http --url "http://localhost:6006/mcp" --scope project
```
## Detection Pattern
Before using Storybook MCP tools, check availability:
```python
# Probe for storybook-mcp tools
ToolSearch(query="+storybook list-all-documentation")
# If tools found → Storybook MCP is available
# If not found → fallback to filesystem-based component discovery
```
## Rule Details
Load rules on demand with `Read("rules/<file>")`:
| Rule | Impact | Description |
|------|--------|-------------|
| `component-discovery` | HIGH | Use list-all-documentation + get-documentation before generating new components |
| `story-preview-verification` | HIGH | Embed preview-stories URLs for visual confirmation |
| `mcp-test-runner` | CRITICAL | Run run-story-tests with a11y:true after component generation |
## Toolset Selection
Filter toolsets via `X-MCP-Toolsets` header to reduce agent context:
| Agent Role | Toolsets | Rationale |
|------------|----------|-----------|
| component-curator | `docs` | Inventory + props only, no testing |
| frontend-ui-developer | `dev,docs,testing` | Full access for gen → verify loop |
| design-system-architect | `docs` | Component metadata for governance |
## Chromatic Remote Publishing
For teams using Chromatic, the docs toolset is publishable remotely:
- Published at `https://<chromatic-storybook-url>/mcp`
- Only docs toolset available remotely (dev + testing need local Storybook)
- Useful for cross-team design system discovery without running Storybook locally
## Graceful Degradation
| Storybook MCP | Fallback | Behavior |
|---------------|----------|----------|
| Available | — | Use MCP tools for component discovery, testing, previews |
| Unavailable | Filesystem | `Glob("**/components/**/*.tsx")` + `Grep` for component inventory |
| Unavailable | 21st.dev | Search public registry via 21st-dev-magic MCP |
| Unavailable | Manual | Claude multimodal analysis of screenshots |
## Related Skills
- `storybook-testing` — CSF3 patterns, Vitest integration, Chromatic TurboSnap
- `component-search` — 21st.dev registry search (external components)
- `design-to-code` — Full mockup-to-component pipeline (uses this skill in Stage 2)
- `ui-components` — shadcn/ui + Radix component patterns
© OrchestKit · MIT · yonatangross/orchestkit