storybook

Driving the twig:storybook MCP server

The twig:storybook MCP server exposes Twig's published Storybook (hosted on Chromatic) as documentation tools. Use it to look up real component props, variants, usage examples, and stories before writing or reviewing code that uses a Twig UI component. Only Docs tools are published — there are no development or testing tools.

The three tools and the order to use them

The tools form a pipeline. Don't skip the discovery step and don't guess IDs.

Tool	Use it to
mcp__plugin_twig_storybook__list-all-documentation	Discover available component and docs IDs. Call this first.
mcp__plugin_twig_storybook__get-documentation	Retrieve full docs, props, usage examples, and stories for one id.
mcp__plugin_twig_storybook__get-documentation-for-story	Get docs for a specific story variant not included in the component docs.

Standard workflow:

1. Call list-all-documentation once at the start to get the catalog of IDs. Pass withStoryIds: true when you also need story IDs to feed into get-documentation-for-story.
2. Find the component you care about in that list and call get-documentation with its id.
3. Only if you need a variant not covered by the component docs, call get-documentation-for-story with a story ID from step 1.

Rules

• Never assume props, variants, or API shape. Retrieve documentation before using a component.
• Don't invent. If a component or prop isn't documented, say it wasn't found — don't guess at it.
• Only use IDs returned by list-all-documentation. Don't fabricate or guess IDs.

Auth

The server uses Chromatic OAuth (our Storybook is private). If the tools aren't available, authenticate via /mcp. Config lives in plugins/twig/.mcp.json under the storybook entry.