IGDS Storybook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load-storybookB | Load IGDS Storybook data for a specific framework or all frameworks |
| list-componentsA | List all available IGDS components for a specific framework |
| get-componentC | Get detailed documentation for a specific IGDS component |
| get-component-sourceA | Get source code structure for a component (properties, CSS, defaults). Requires cached data. |
| search-componentsC | Search for IGDS components across all frameworks |
| get-storyB | Get a specific story entry by its ID |
| compare-componentB | Compare a component across Angular, React, and Core-Web frameworks |
| get-component-storiesB | Get all story variants for a component |
| get-component-cssA | Get CSS styles for a component. Requires cached data. |
| get-story-examplesA | Get rendered HTML examples from Storybook stories for a component |
| get-statsB | Get statistics about loaded storybook data |
| zeroheight-list-categoriesA | List all component categories from Zeroheight design system documentation |
| zeroheight-list-componentsA | List components from Zeroheight (optionally filtered by category) |
| zeroheight-get-componentA | Get full component documentation from Zeroheight |
| zeroheight-get-sectionA | Get a specific section (design/code/usage/accessibility) for a component |
| zeroheight-searchB | Search across all Zeroheight content |
| zeroheight-get-storybook-refB | Get Storybook cross-references for a Zeroheight component |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Several tools overlap in purpose: list-components vs search-components vs zeroheight-list-components all deal with component discovery, and get-component vs zeroheight-get-component both retrieve component docs. Story-related tools (get-story, get-component-stories, get-story-examples) have distinct but somewhat ambiguous boundaries. Descriptions help, but an agent may struggle to pick the right tool without careful reading.
Naming is inconsistent: most tools use kebab-case with verb-noun (get-stats, list-components), but zeroheight tools use a 'zeroheight-' prefix with camelCase (zeroheight-search, zeroheight-list-categories). There is no uniform verb convention (get, list, search, load, compare), and the mix of styles reduces predictability.
With 17 tools, the server is on the heavy end but each tool addresses a specific need (storybook data, Zeroheight docs, comparisons, CSS, examples). The scope is broad enough to justify the count, though it could be streamlined by merging some overlapping component/story tools.
The domain is well-covered: data loading, listing, searching, retrieving details, stories, CSS, examples, and Zeroheight integration. The only minor gap is lack of explicit framework management (e.g., unloading data) but this is a read-only documentation server, so core workflows are complete.