@viantotech/mcp-storybook
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache TTL in seconds | 300 |
| CACHE_ENABLED | No | Cache enabled (true/false) | true |
| STORYBOOK_BASE_URL | Yes | URL of your Storybook deployment | |
| STORYBOOK_AUTH_TYPE | No | Auth type | none |
| STORYBOOK_CLIENT_ID | No | OAuth client ID | |
| STORYBOOK_DATA_SOURCE | No | Data source | auto |
| STORYBOOK_ACCESS_TOKEN | No | Bearer token | |
| STORYBOOK_CLIENT_SECRET | No | OAuth client secret | |
| STORYBOOK_REFRESH_TOKEN | No | OAuth refresh token | |
| STORYBOOK_SESSION_COOKIE | No | Session cookie value | |
| STORYBOOK_BASIC_AUTH_PASSWORD | No | Basic auth password | |
| STORYBOOK_BASIC_AUTH_USERNAME | No | Basic auth username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_storiesC | List Story Book entries (metadata only, no full content). |
| search_storiesB | Search stories by title, description, tags, sections, and content. |
| get_storyB | Get a full story with optional content length cap. |
| get_story_sectionC | Get one section from a story. |
| get_story_metadataB | Get story metadata without loading full content. |
| list_componentsB | List UI components from Storybook (grouped), e.g. Components/Button, Components/Alert. Metadata only. |
| get_componentB | Get one component by name or path (Alert, Components/Alert). Includes docs overview and story variant ids. |
| get_component_configA | Storybook Controls config per component: argTypes (variant, size, …) and stylePresets (Default, Secondary, …) with args. |
| get_design_tokensA | Extract design tokens (colors, spacing, typography, shadows, etc.) from Storybook CSS variables. |
| get_component_dependenciesB | Get component dependency graph: which components a component uses, and which components use it. |
| map_figma_componentA | Map a Figma component name/node/URL to the corresponding Storybook component with suggested props. |
| find_stories_by_source_fileA | Reverse lookup: given a component source file path, find matching Storybook stories. |
| preview_storyB | Build a Storybook iframe preview URL for a story with optional args, globals, and viewport. |
| get_story_instructionsA | Get best-practice instructions for writing Storybook stories (CSF3, argTypes, play functions). |
| get_component_usageB | Get copy-paste-ready component usage code (import + JSX) built from story argTypes and preset args. |
| compare_versionsB | Compare two Storybook deployments and return structured diff (added/removed/modified components, prop changes). |
| get_story_contextB | Retrieve concise Story Book context for a natural-language question. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| stories-index | Metadata for all stories (no full content). |
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes, but the several story retrieval variants (get_story, get_story_metadata, get_story_section, get_story_context) could cause misselection if an agent doesn't read descriptions carefully. Descriptions are detailed enough to resolve most ambiguity.
All tool names follow a consistent snake_case verb_noun pattern (get_, list_, search_, map_, find_, preview_, compare_). There is no mixing of conventions or vague generic verbs.
With 17 tools, the set falls into the 16-25 heavy range. The Storybook domain is broad, but several tools are highly granular and could potentially be consolidated.
The tool surface covers the full Storybook workflow: discovering components and stories, retrieving story details and metadata, getting config/usage, previewing, comparing versions, and mapping from Figma/source files. No critical operations appear to be missing.