Skip to content

Release history

storybookjs/addon-mcp releases

Help agents automatically write and test stories for your UI components.

Back to tool Latest release

All releases

49 shown

@storybook/[email protected] New feature
Notable features
  • Support Storybook component manifests that use `reactComponentMeta` for React prop extraction
Full changelog

Patch Changes

  • #206 70b5b23 Thanks @kasperpeulen! - Support Storybook component manifests that use reactComponentMeta for React prop extraction.

    This keeps MCP documentation output working when Storybook is configured to emit the newer
    reactComponentMeta payload instead of reactDocgen or reactDocgenTypescript.

  • #204 b2a327d Thanks @JReinhold! - upgrade tmcp dependencies

View release on GitHub
@storybook/[email protected] New feature
Notable features
  • Added server-level instructions to both @storybook/mcp and @storybook/addon-mcp in the MCP initialize response.
  • Forwarded `sources` through `createStorybookMcpHandler()` into per-request transport context.
Full changelog

Minor Changes

  • #185 c5439b7 Thanks @copilot-swe-agent! - Add MCP server-level instructions to both packages

    Both @storybook/mcp and @storybook/addon-mcp now include server instructions in the MCP initialize response. These instructions guide agents on how to use the available tools effectively without requiring explicit prompting from users.

Patch Changes

  • #194 eb0ea73 Thanks @JReinhold! - Forward sources through createStorybookMcpHandler() into the per-request transport context.
View release on GitHub
@storybook/[email protected] New feature
Notable features
  • Server-level instructions included in MCP `initialize` response for both @storybook/mcp and @storybook/addon-mcp
Full changelog

Minor Changes

  • #185 c5439b7 Thanks @copilot-swe-agent! - Add MCP server-level instructions to both packages

    Both @storybook/mcp and @storybook/addon-mcp now include server instructions in the MCP initialize response. These instructions guide agents on how to use the available tools effectively without requiring explicit prompting from users.

Patch Changes

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Renamed config key `experimentalComponentsManifest` to `componentsManifest`
Full changelog

Patch Changes

  • #181 ff217d8 Thanks @copilot-swe-agent! - Rename feature flag experimentalComponentsManifest → componentsManifest

    The Storybook feature flag has been renamed from experimentalComponentsManifest to componentsManifest and now defaults to true in Storybook core.

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Renamed configuration key `experimentalComponentsManifest` to `componentsManifest` and changed its default value to `true`.
Full changelog

Patch Changes

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Renamed exported function `addGetComponentStoryDocumentationTool` to `addGetStoryDocumentationTool` in @storybook/mcp.
Notable features
  • Added story ID based inputs for preview and testing workflows.
  • Surface story IDs in docs outputs with `withStoryIds` flag and include them in story sections.
Full changelog

Minor Changes

  • #171 b3a8356 Thanks @copilot-swe-agent! - Export addGetStoryDocumentationTool directly instead of renaming it to addGetComponentStoryDocumentationTool.

    Breaking change: If you were importing addGetComponentStoryDocumentationTool from @storybook/mcp, update your import to use addGetStoryDocumentationTool instead.

Patch Changes

  • #175 6a098f9 Thanks @JReinhold! - Add story ID based inputs for preview/testing workflows and surface story IDs in docs outputs.

    This change keeps existing path-based story inputs (absoluteStoryPath + exportName) while adding a storyId input shape for preview-stories and run-story-tests. It also adds withStoryIds to list-all-documentation and includes story IDs in get-documentation story sections, so agents can discover and reuse IDs directly without extra filesystem lookup steps.

View release on GitHub
@storybook/[email protected] New feature
⚠ Upgrade required
  • Dependency bump: @storybook/mcp updated to version 0.5.0.
Notable features
  • Added `storyId` input shape for `preview-stories` and `run-story-tests`, keeping existing path-based inputs.
  • Introduced `withStoryIds` option in `list-all-documentation` and included story IDs in `get-documentation` outputs.
Full changelog

Patch Changes

  • #171 b3a8356 Thanks @copilot-swe-agent! - Fix: expose the get-documentation-for-story tool in the MCP Addon.

  • #176 8afbb72 Thanks @JReinhold! - Improve preview-stories tool description to make agent behavior more consistent.

  • #175 6a098f9 Thanks @JReinhold! - Add story ID based inputs for preview/testing workflows and surface story IDs in docs outputs.

    This change keeps existing path-based story inputs (absoluteStoryPath + exportName) while adding a storyId input shape for preview-stories and run-story-tests. It also adds withStoryIds to list-all-documentation and includes story IDs in get-documentation story sections, so agents can discover and reuse IDs directly without extra filesystem lookup steps.

  • Updated dependencies [b3a8356, 6a098f9]:

View release on GitHub
@storybook/[email protected] New feature
Notable features
  • `run-story-tests` tool available when @storybook/addon-vitest is configured and running Storybook 10.3.0-alpha.8 or above; reports a11y violations if @storybook/addon-a11y is also configured.
Full changelog

Patch Changes

  • #131 9cf991c Thanks @JReinhold! - Added run-story-tests tool that is available when:

    1. @storybook/addon-vitest is configured
    2. Running Storybook 10.3.0-alpha.8 or above

    Additionally, if @storybook/addon-a11y is configured, the tool returns accessibility violations too.

  • Updated dependencies [9cf991c]:

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Removed support for XML format; related configuration option has no effect, output is always markdown.
Notable features
  • Added multi-source composition with OAuth for private Storybooks
Full changelog

Minor Changes

  • #165 e088e05 Thanks @JReinhold! - Remove support for XML format.

    Breaking Change

    The related option to configure XML vs markdown format now has no impact, the output is always formatted as markdown.

  • #140 f9fce2a Thanks @kasperpeulen! - Add multi-source composition with OAuth for private Storybooks

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Removed support for XML output format; the option to configure XML vs markdown no longer affects behavior and markdown is always produced.
Notable features
  • Added multi-source composition with OAuth for private Storybooks
Full changelog

Minor Changes

  • #165 e088e05 Thanks @JReinhold! - Remove support for XML format.

    Breaking Change

    The related option to configure XML vs markdown format now has no impact, the output is always formatted as markdown.

  • #140 f9fce2a Thanks @kasperpeulen! - Add multi-source composition with OAuth for private Storybooks

Patch Changes

View release on GitHub
@storybook/[email protected] Bug fix

Fixed regression so component‑attached MDX docs are rendered in markdown output for get-documentation.

Full changelog

Patch Changes

  • #123 b7aeb40 Thanks @valentinpalkovic! - Minimize token usage by only including the 3 first stories in component documentation.

    ... if there are already prop types. If there are no prop types, include all stories. Additional stories can be fetched individually using a new get-documentation-for-story tool.

  • #160 bab8ec9 Thanks @JReinhold! - Render component-attached MDX docs entries in markdown output for get-documentation.

    This fixes a regression where docs attached to components via component.docs in components.json were not included in markdown responses. The markdown formatter now emits a ## Docs section below stories (and before props).

View release on GitHub
@storybook/[email protected] Breaking risk

Fixed regression: component-attached MDX docs entries now appear in markdown output for `get-documentation`.

Full changelog

Patch Changes

  • #141 03e957d Thanks @shilman! - Upgrade deprecated MCP server methods

  • #160 bab8ec9 Thanks @JReinhold! - Render component-attached MDX docs entries in markdown output for get-documentation.

    This fixes a regression where docs attached to components via component.docs in components.json were not included in markdown responses. The markdown formatter now emits a ## Docs section below stories (and before props).

  • Updated dependencies [b7aeb40, bab8ec9]:

View release on GitHub
@storybook/[email protected] New feature
Notable features
  • Support for MCP App: renders Storybook stories directly in agent chat of compatible MCP clients
Full changelog

Patch Changes

  • #134 457b349 Thanks @JReinhold! - Add support for MCP App, rendering stories directly in the agent chat in MCP clients that support it
View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Renamed CLI/tool `get-ui-building-instructions` → `get-storybook-story-instructions`
Notable features
  • Updated storybook‑story building instructions template to clarify what constitutes a good story
  • Added extensive description for the `get-storybook-story-instructions` tool to guide agents on proper usage
Full changelog

Minor Changes

  • #118 bafbfc6 Thanks @valentinpalkovic! - Renamed tool get-ui-building-instructions to get-storybook-story-instructions to increase the likelihood of Agents calling the MCP tool.

    Further updates:

    • Updated storybook-story building instructions template to be more specific about what a good story is.
    • Added an extensive description for the get-storybook-story-instructions tool to give agents more information of when to call the MCP tool

Patch Changes

  • #128 20d97e2 Thanks @JReinhold! - Fix disabled docs toolset in Storybook version prior to v10.2.0-alpha.10
View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Renamed `addGetComponentDocumentationTool` to `addGetDocumentationTool`
  • Renamed `addListAllComponentsTool` to `addListAllDocumentationTool`
  • Renamed hook `onListAllComponents` to `onListAllDocumentation`
Notable features
  • Added support for docs entries in manifests sourced by MDX files
Full changelog

Minor Changes

  • #120 c1fc816 Thanks @JReinhold! - Add support for docs entries in manifests, sourced by MDX files.

    Breaking Changes

    This change introduces a number of minor breaking changes to @storybook/mcp:

    1. The lower level tool adder functions have been renamed:
    2. addGetComponentDocumentationTool -> addGetDocumentationTool
    3. addListAllComponentsTool -> addListAllDocumentationTool
    4. The optional tool hooks have been renamed:
    5. onListAllComponents -> onListAllDocumentation
    6. onGetComponentDocumentation -> onGetDocumentation
    7. The exported MANIFEST_PATH constant have been removed in favor of two new constants, COMPONENT_MANIFEST_PATH and DOCS_MANIFEST_PATH
View release on GitHub
@storybook/[email protected] Security relevant
Security fixes
  • Updated Valibot from v1.1.0 to v1.2.0, fixing three security vulnerabilities
Full changelog

Patch Changes

  • #105 e27f6b2 Thanks @copilot-swe-agent! - Update Valibot to v1.2.0 to fix security vulnerabilities

    Valibot 1.1.0 contained 3 security vulnerabilities that are addressed in v1.2.0. This is a non-breaking security patch - no changes required for consumers.

View release on GitHub
@storybook/[email protected] Security relevant
Security fixes
  • Valibot upgraded from v1.1.0 to v1.2.0 fixing three security vulnerabilities
Full changelog

Patch Changes

  • #105 e27f6b2 Thanks @copilot-swe-agent! - Update Valibot to v1.2.0 to fix security vulnerabilities

    Valibot 1.1.0 contained 3 security vulnerabilities that are addressed in v1.2.0. This is a non-breaking security patch - no changes required for consumers.

  • Updated dependencies [e27f6b2]:

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Removed `source` property from context; replaced with `request` object.
Full changelog

Minor Changes

  • #54 5d18405 Thanks @JReinhold! - Replace the source property in the context with request.

    Now you don't pass in a source string that might be fetched or handled by your custom manifestProvider, but instead you pass in the whole web request. (This is automatically handled if you use the createStorybookMcpHandler() function).

    The default action is now to fetch the manifest from ../manifests/components.json assuming the server is running at ./mcp. Your custom manifestProvider()-function then also does not get a source string as an argument, but gets the whole web request, that you can use to get information about where to fetch the manifest from. It also gets a second argument, path, which it should use to determine which specific manifest to get from a built Storybook. (Currently always ./manifests/components.json, but in the future it might be other paths too).

Patch Changes

View release on GitHub
@storybook/[email protected] Maintenance
⚠ Upgrade required
  • Peer dependency allowance updated to support Storybook 10.1.0 prereleases
  • Telemetry payload includes new toolset information
Notable features
  • Docs toolset now outputs markdown configurable via experimentalOutput option
Full changelog

Patch Changes

View release on GitHub
@storybook/[email protected] New feature
Notable features
  • GET handler serves HTML when visiting /mcp and redirects to human‑readable component manifest
  • Updated manifest format
Full changelog

Patch Changes

  • #50 0334d29 Thanks @JReinhold! - Add GET handler that serves HTML when visiting /mcp, and redirects to human-readable component manifest when applicable

  • #50 0334d29 Thanks @JReinhold! - Update manifest format

View release on GitHub
@storybook/[email protected] New feature
Notable features
  • Optional "enabled" function added to directly exported tool adders for dynamic enable/disable behavior
Full changelog

Patch Changes

  • #48 52be338 Thanks @JReinhold! - Add optional "enabled" function to the directly exported tool adders. This allow you to define a function that will dynamically enable/disable the tool however you want, eg. per request condition

  • #51 2028709 Thanks @paoloricciuti! - chore: update tmcp

View release on GitHub
@storybook/[email protected] Breaking risk
Breaking changes
  • Requires minimum Storybook version 10.1 (canary) for @storybook/addon-mcp; users on Storybook 9 or 10.0 must use package version 0.0.9.
Notable features
  • Adds Webpack support, enabling usage with Next.js and other Webpack‑based frameworks
Full changelog

Minor Changes

  • #36 93f88e4 Thanks @JReinhold! - Add support for Webpack (including Webpack-based frameworks like Next.js)

    Breaking Change

    This requires version 10.1 of Storybook, currently only available as the canary version 0.0.0-pr-32810-sha-6e759c7e. If you want to continue to use the addon with Storybook 9 or 10.0 (and Vite), stick to version 0.0.9 of this package.

EDIT: The above is not true anymore, see version 0.1.1 of this package.

Patch Changes

View release on GitHub
@storybook/[email protected] New feature
Notable features
  • Support passing a custom `manifestProvider` option to the MCP server, defaulting to `fetch()`.
  • Exported merge tools for integration into other MCP servers (e.g., tmcp).
Full changelog

Patch Changes

  • #32 531a2d4 Thanks @copilot-swe-agent! - Support passing in a custom manifestProvider option to the MCP server, falling back to fetch() as the default

  • #33 ae6ab44 Thanks @JReinhold! - Export tools to be merged into other MCP servers.

    Currently only tmcp-based MCP servers supports using these tools directly.

View release on GitHub
@storybook/[email protected] New feature
⚠ Upgrade required
  • Requires Storybook v10.1 prerelease (canary `0.0.0-pr-32810-sha-af0645cd`).
  • Enable experimental flag `features.experimentalComponentsManifest = true` in the main config.
  • Only React-based frameworks support component manifest generation currently.
Notable features
  • Tools to generate component documentation based on the components manifest
Full changelog

Patch Changes

  • #33 ae6ab44 Thanks @JReinhold! - Add tools to get documentation for components, based on the component manifest being generated in the Storybook dev server.

    Requirements:

    1. That the experimental feature flag features.experimentalComponentsManifest is set to true in the main config.
    2. Only React-based frameworks supports component manifest generation for now.
    3. Requires Storybook v10.1 (prereleases), which at the time of writing is available as a canary version 0.0.0-pr-32810-sha-af0645cd.

  • Updated dependencies [531a2d4, ae6ab44]:

View release on GitHub
v0.0.3 New feature
Notable features
  • Improved UI building instructions
  • Enhanced output format of Get Story URLs tool
  • Added basic telemetry for sessions and tool calls
Full changelog

Patch Changes

  • #11 bba9b8c Thanks @JReinhold! - - Improved UI Building Instructions

    • Improved output format of Get Story URLs tool

  • #9 e5e2adf Thanks @JReinhold! - Add basic telemetry for sessions and tool calls

View release on GitHub

Beta — feedback welcome: [email protected]