Storybook

Storybook MCP Connector for Claude

A+

Connect your AI to Storybook. Explore your design system, inspect UI components, and retrieve implementation guidance programmatically.

6 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Seamlessly integrate your Storybook design system into your conversational AI workflows. Empower front-end engineers and designers to instantly query component libraries, retrieve prop signatures, and extract documentation paths natively within their terminal. By connecting your deployed Storybook instance directly to your AI context, you eliminate context switching, prevent duplicate UI implementations, and accelerate component-driven architecture development across your entire front-end ecosystem.

What you can do

  • Design System Discovery — Systematically map your component folder structures invoking list_categories and browse all rendered elements across your UI utilizing list_components.
  • Component Inspection — Quickly lookup predefined interface elements utilizing search_components to avoid code duplication, and retrieve component properties and metadata via get_story_args.
  • Implementation Guidance — Extract local source code paths directly from the Storybook index using extract_docs_guidance to efficiently evaluate implementation logic.
  • Visual Previews — Generate interactive, isolated sandbox iframe endpoints by running get_preview_url to safely preview changes before integrating.

How it works

  1. Install the Storybook MCP module into your local AI configuration.
  2. In the connection parameters, simply provide your deployed STORYBOOK_URL.
  3. Storybook generates a static index.json inherently; the MCP natively reads this JSON index to retrieve your entire frontend component hierarchy.
  4. Prompt your AI: "Search the Storybook components for 'Button', detail its default arguments, and generate an isolated preview URL."

Who is this for?

  • Frontend Engineers — Rapidly discover existing UI elements and their expected properties without leaving your coding interface.
  • UI/UX Designers — Validate and audit deployed component structures programmatically, ensuring implementation aligns exactly with design tokens.
  • Technical Writers — Extract existing Storybook documentation pathways automatically to maintain consistent, up-to-date design system guidelines.
ui-componentsdesign-systemcomponent-libraryfrontend-developmentui-testingdocumentation

6 tools expose this connector's capabilities to your AI agent.

extract_docs_guidance

Get guidance on how to read documentation for a component

get_preview_url

Generate the preview URL for a component sandbox

get_story_args

Get metadata and default arguments for a specific component

list_categories

g., Atoms, Molecules, Organisms). List the top-level categories and folder structure of the Design System

list_components

You can optionally filter by category folder. List all UI components available in the Storybook Design System

search_components

Search for specific components by name or keyword

See how to talk to your AI agent using Storybook.

Search for Button components in my Storybook and show their props.

Scanning Storybook index... **Discovered UI Matches (`search_components`)**: - `Button/Primary-Action` (ID: comp-btn-01) - `Button/Ghost` (ID: comp-btn-02) Inspecting props via `get_story_args` on `Button/Primary-Action`: - **Props**: `label` (string), `isActive` (boolean), `variant` (primary/secondary), `onClick` (function). I can generate an isolated preview URL if needed.

List the categories in the design system and browse the components rendered.

Mapping the interface structure... **Categories (`list_categories`)**: - `Atoms` - `Molecules` - `Layouts` **Components (`list_components`)**: - `Atoms/Input` - `Atoms/Tooltip` - `Layouts/Sidebar` Documentation endpoints have been dynamically assembled.

Extract the local source code paths from the index for the Navigation Bar component and generate an iframe preview.

Checking local references logically... **Source Paths (`extract_docs_guidance`)**: Resolved path: `./src/components/NavBar.tsx`. Documentation notes suggest importing `NavProps` directly. **Preview Generated (`get_preview_url`)**: The isolated sandbox iframe is ready at `//storybook-instance/iframe.html?id=layout-navbar--default`.

No. The MCP reads the static `index.json` file generated by your Storybook build. As long as the agent can reach the `STORYBOOK_URL` over the network, no additional authentication is needed.

Related Connectors