Vinkius

Storybook MCP. Inspect component structure and usage instantly.

Storybook MCP connects your AI client directly to your design system's component library. You can programmatically browse every UI element, inspect specific components for their properties and metadata, locate documentation paths, and generate isolated preview URLs—all without leaving your coding environment.

Storybook MCP is compatible with Claude Claude
Storybook MCP is compatible with ChatGPT ChatGPT
Storybook MCP is compatible with Cursor Cursor
Storybook MCP is compatible with Gemini Gemini
Storybook MCP is compatible with Windsurf Windsurf
Storybook MCP is compatible with VS Code VS Code
Storybook MCP is compatible with JetBrains JetBrains
Storybook MCP is compatible with Vercel Vercel
See Vinkius in Action

Give Claude and any AI agent real-world access

Map design system structure

List the top-level categories and folder organization of your component library.

Search for components by name

Find specific UI elements within the Storybook based on a keyword or partial name.

Get component metadata

Retrieve detailed information, including default arguments and expected properties, for any given component.

Generate sandbox previews

Create temporary, isolated URLs so you can safely preview how a component will look before implementing it.

Locate source documentation paths

Extract local source code file paths and implementation notes directly from the Storybook index.

Waiting for input…

AI Agent
Storybook

What AI agents can do with Storybook: 6 Tools for Component Inspection

Use these tools to programmatically list components, retrieve metadata, find source paths, and validate your entire design system's component library.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Storybook MCP

Extract Docs Guidance

Gets guidance on how to read documentation for a component by extracting its local source code paths.

Get Preview Url

Generates the unique URL needed to run an isolated sandbox preview of a component's...

Get Story Args

Retrieves detailed metadata and default arguments, such as required props, for a...

List Categories

Lists the top-level structural categories (like Atoms or Molecules) that organize...

List Components

Provides a complete list of all available UI components within the entire Storybook...

Search Components

Searches for specific components using keywords or partial names across the design system index.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Storybook MCP is compatible with Claude

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Storybook integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on each call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Storybook, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,200+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Connections are secured and governed automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog weekly
Storybook MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Storybook. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS CLOUD

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on each call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Component documentation and props are always out of sync.

Right now, figuring out a component's required properties is a nightmare. You have to jump between the design spec sheet, the Storybook live view, and finally the actual source code file. Then you copy-paste prop names, hoping they haven't changed since last week.

With this MCP connected through Vinkius, your agent reads the component definition directly. You just ask it what props a component needs—it gives you the name, type, and default value immediately. The friction is gone.

Storybook MCP: Get immediate structural context.

Instead of manually running `ls` commands or traversing folder structures in a file explorer to map out the design system, you can ask your agent to run `list_categories`. It maps the entire hierarchy for you. Then use `list_components` to drill down into every single element.

The process shifts from manual exploration to conversational discovery. You get a complete, structured inventory of every component available in the library, instantly.

What Storybook MCP does for your AI

Your AI agent can now treat your Storybook instance like a functional part of your codebase. Instead of opening a dozen tabs to check component props or find the source code structure, you just ask it. It maps out your entire design system—from top-level categories down to individual atoms. You'll stop wasting time jumping between documentation sites and your IDE.

This MCP lets you query component libraries for default arguments and validate complex prop signatures instantly. Whether you're mapping out the overall architecture using Vinkius, or just trying to confirm if a Button component supports an 'isLoading' state, the data is right there in your context. You get immediate feedback on how components are structured, what source paths they rely on, and even isolated sandbox previews for testing changes before committing any code.

Built · Hosted · Managed by Vinkius Storybook MCP - Inspect Component Libraries & Props
Server ID 019d760d-ba7d-7209-a875-6eb00b2db2be
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Frequently asked questions about Storybook MCP

How do I use Storybook MCP to find out what props a component needs? +

You ask your agent to check a specific component. The MCP uses get_story_args and returns a clean list of all necessary properties, their data types, and whether they have default values.

Can Storybook MCP help me see how a component looks before coding it? +

Yes. You prompt the agent for a preview URL. It runs get_preview_url to generate an isolated sandbox iframe, letting you validate the visual output safely.

Which tool should I use if I want to see all available components? +

Use list_components. This function gives you a comprehensive inventory of every single UI element defined in your entire design system, organized by category.

Does Storybook MCP help with documentation linking? +

Yes. You can use extract_docs_guidance to pull the local source code paths and relevant implementation notes directly from the index, saving you manual file searching.

What if I only know a keyword for a component? +

No problem. Use search_components. It finds components by name or partial keywords across the whole library, narrowing down your focus quickly.