Storybook Mcp Integration

Community

yonatangross

storybook-mcp-integration

Reference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a mockup into a new component and consumes these tools as one stage, use design-to-code.

Overview

Publisher	yonatangross
Repository	`orchestkit`
Skill name	`storybook-mcp-integration`
Stars	298
Forks	35
Bundled files	5
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
5 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by yonatangross on GitHub. Read the source before you install it.

Installation

Install the Storybook Mcp Integration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/storybook-mcp-integration
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/storybook-mcp-integration

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/yonatangross/orchestkit.git /tmp/orchestkit
mkdir -p .claude/skills
cp -r /tmp/orchestkit/plugins/ork/skills/storybook-mcp-integration .claude/skills/storybook-mcp-integration

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Storybook Mcp Integration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Storybook Mcp Integration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Storybook Mcp Integration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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/addon-mcp@0.6.0, 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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Storybook Mcp Integration AI skill do?

Why use Storybook Mcp Integration on TypingMind?

Because you install it once and use it with any model. Storybook Mcp Integration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Storybook Mcp Integration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/storybook-mcp-integration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Storybook Mcp Integration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Storybook Mcp Integration?

As many as you like. As long as a model supports skills, you can use Storybook Mcp Integration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Storybook Mcp Integration AI skill free?

Yes. It is published on GitHub by yonatangross under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Storybook MCP Integration

When to Use

Quick Reference — 6 Tools, 3 Toolsets

Prerequisites

Detection Pattern

Rule Details

Toolset Selection

Chromatic Remote Publishing

Graceful Degradation

Related Skills

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now