pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Storybook MCP Addon

Pod holds 23 of 44 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Storybook MCP Addon.

Most discussed

Enable private vulnerability reporting

Hi,

I have a security finding to share privately. Could you enable private vulnerability reporting on this repo?

Thanks

Read the thread · 2026-06-15 · closed · external user · 3 comments

OAuth authentication fails with Claude Code CLI and claude.ai MCP clients

Summary

When using @storybook/addon-mcp with a private Chromatic-hosted Storybook, the MCP OAuth flow fails when connecting via Claude Code CLI or claude.ai Cowork. The browser opens for authentication but lands on an authentication error page.

Environment

  • @storybook/addon-mcp: 0.4.2
  • MCP client: Claude Code CLI / claude.ai Cowork
  • Storybook hosted on Chromatic (private, OAuth-protected)

Steps to reproduce

  1. Set up @storybook/addon-mcp on a private Chromatic-hosted Story

Read the thread · 2026-04-07 · open · external user · 5 comments

Components Manifest finds A LOT of story errors

I just tried the mcp addon and got this:

Image

I get it's more of a question than a bug report.

Most errors are like this (we are using CSF Next):

Image

Because the previous developer extracted all renders to variables, while it looks like we

Read the thread · 2026-03-02 · closed · external user · 3 comments

Sharing MCP CLI as a package

Hey,

We've started using the @storybook/mcp package to share a CLI with our React design system library package so other teams can run a local stdio MCP server for agents to pull design system component docs.

I wrote up what we're doing here: https://alexocallaghan.com/react-design-system-library-mcp

Is this going to be a supported approach? Looking at this issue (https://github.com/storybookjs/mcp/issues/138) it looks like pulling from remote Storybooks might be more of the focus?

One thi

Read the thread · 2026-02-02 · closed · external user · 5 comments

Support for react-docgen-typescript

Would it be possible to generate document manifest with either react-docgen or react-docgen-typescript?

I would expect the addon to work with the reactDocgen option in storybook config and generate the component manifest with it. https://storybook.js.org/docs/api/main-config/main-config-typescript#reactdocgen

So far I am running into missing props in the generated manifest because of it.

Read the thread · 2026-01-29 · closed · external user · 2 comments

Docs Tools (Experimental) unavailable

Describe the bug

Can't get Docs Tools (Experimental) via MCP Inspector

Steps to reproduce the behavior

  1. npm i storybook@10.1.0 (also tired with 10.2.0-alpha.0)
  2. npx storybook add @storybook/addon-mcp
  3. Update config
  import type { StorybookConfig } from '@storybook/react-vite';

const config: StorybookConfig = {
  core: {
    disableWhatsNewNotifications: true,
    disableTelemetry: true,
    enableCrashReports: false,
  },
  stories: ['../src/**/*.mdx', '../

[Read the thread](https://github.com/storybookjs/mcp/issues/91) · 2025-11-27 · closed · external user · 6 comments

### [Bug] Unable to connect with Claude Code using version 0.1.0

### Describe the bug

I am no longer able to connect a fresh Claude Code installation to the `addon-mcp` server.

I say "fresh" because I am testing on 2 laptops - one is still working, but was configured before the recent refactor, albeit through the SB hosted in this project.

### Steps to reproduce the behavior

> I suspect you need an installation of Claude that has never been connected to the MCP server before, but that is speculation right now. I am unable to confirm at the moment.

1. Ins

[Read the thread](https://github.com/storybookjs/mcp/issues/47) · 2025-10-28 · closed · external user · 7 comments

### [Bug] Storybook instance crashes when MCP server attempts to connect

### Describe the bug

Storybook (8.6.14) instance crashes when MCP server attempts to connect.

### Steps to reproduce the behavior

1. Install the MCP server using `npx storybook add @storybook/addon-mcp`
2. Add the MCP server to Claude Code with `claude mcp add storybook-mcp --transport http http://localhost:6006/mcp --scope project`
3. Run the Storybook instance
4. Run Claude Code

The storybook instance crashes and Claude Code cannot connect to the MCP server.

### Expected behavior

The MCP

[Read the thread](https://github.com/storybookjs/mcp/issues/14) · 2025-09-04 · closed · external user · 3 comments

## Most recent

### addon-mcp: X-MCP-Toolsets request header fully replaces the configured toolsets — config acts as a default, not an allowlist

### Package / versions

- `@storybook/addon-mcp`: 0.7.0
- Storybook: 10 (`storybook` 10.4.x CLI, `@storybook/react-vite` 10.5.x)

### Configuration

`.storybook/main.ts` enables only the docs toolset:

```ts
addons: [
  {
    name: '@storybook/addon-mcp',
    options: {
      toolsets: { dev: false, test: false, docs: true },
    },
  },
],

Observed behavior

Any caller can re-enable toolsets the maintainer explicitly disabled by sending an X-MCP-Toolsets request header. The header **

Read the thread · 2026-08-25 · open · external user · 0 comments

New MCP spec support

Hello dears! I wonder if there's any plan to support the new MCP spec any time soon?

Thanks a lot!

Read the thread · 2026-08-21 · open · external user · 0 comments

list-all-documentation never surfaces component @summary; listing lines truncate mid-description

Summary

list-all-documentation builds each listing line from component.summary ?? description, truncating the description at 90 characters. Nothing populates component.summary: docgen extracts a component-level @summary JSDoc tag into reactDocgenTypescript.tags.summary, but no code path reads it from there. So the tag has no effect and every listing line is truncated description.

Related: #367. Same drop point (component-level JSDoc tags parsed but not carried into formatter outpu

Read the thread · 2026-08-10 · open · external user · 0 comments

Support MCP tool annotations (e.g. readOnlyHint) on registered tools

The provided `list-all-documentation`, `get-documentation`, and `get-documentation-for-story` are all read-only tools, but there's no way for a consumer of @storybook/mcp to set MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint — the standard ToolAnnotations fields) on them. (See latest [schema](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/271ecc9accafdd9b83a3c869fa67c22953b2a

Read the thread · 2026-07-31 · open · external user · 1 comment

[Bug] peerDependencies admit storybook 9.1.x, where the preset fails to load and the components manifest does not exist in core

What happened

I added @storybook/addon-mcp@0.7.0 to a clone of radix-ui/primitives (commit df8f89ac, apps/storybook, storybook 9.1.20). The install succeeded: the published peer range ^0.0.0-0 || ^9.1.16 || ^10.0.0 || ^10.1.0-0 || ^10.2.0-0 || ^10.3.0-0 || ^10.4.0-0 || ^10.5.0-0 admits 9.1.20. storybook build then failed while loading presets:

Error [ERR_INTERNAL_ASSERTION]: Unexpected module status 0

That error masks the cause. Importing the preset directly exposes it:

``

Read the thread · 2026-07-29 · open · external user · 1 comment

[Bug] Sibling components re-exported from the same file all inherit one component's JSDoc & props (related to #216)

Describe the bug

Related to #216, but a different trigger: instead of a parent/subcomponent relationship (Parent.Child = Child), this happens with independent sibling components declared/exported from the same source file. get-documentation (and the underlying manifest) resolves every sibling's docs entry to whichever one component in that file actually has a docgen-visible declaration + JSDoc, overwriting the others' description AND prop tables.

This is especially easy to hit when

Read the thread · 2026-07-23 · open · external user · 0 comments

get-documentation omits component JSDoc tags (@deprecated) from its output

Summary

get-documentation omits component-level JSDoc tags — notably @deprecated — from the markdown it returns. The tag is extracted and present in the manifest/docgen data, but it is dropped when that data is formatted into the tool response. So an agent calling get-documentation cannot see that a component is deprecated unless the deprecation is also written into the prose description by hand.

This reproduces both with and without experimentalDocgenServer. I noticed it while

Read the thread · 2026-07-22 · closed · external user · 0 comments

[Feature Request]: Ability to configure MCPServer's instructions

Storybook MCP already injects some good instructions. It injects INSTRUCTIONS.md here: https://github.com/storybookjs/mcp/blob/main/packages/mcp/bin.ts#L52.

It would be nice if we could override this option with our own instructions. Something like:

import { createStorybookMcpHandler, STORYBOOK_MCP_INSTRUCTIONS } from '@storybook/mcp';

const CUSTOM_INSTRUCTIONS = `
- Always use MUI's color Palette instead 

[Read the thread](https://github.com/storybookjs/mcp/issues/358) · 2026-07-08 · open · external user · 1 comment

### Start Alpha/beta release channel.

### Describe the bug

A clear and concise description of what the bug is.

### Steps to reproduce the behavior

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

### Expected behavior

A clear and concise description of what you expected to happen.

### Screenshots and/or logs

If applicable, add screenshots and/or logs to help explain your problem.

### Environment

 - OS: [e.g. iOS]
 - Node.js version: [e.g. v12.17.0]
 - NPM version: [e.g. 6.14.4]
 - Browser (if applicab

[Read the thread](https://github.com/storybookjs/mcp/issues/342) · 2026-07-07 · closed · outside contributor · 0 comments

### [Bug] Unable to compose MCP servers on Chromatic hosted storybooks

### Describe the bug

When publishing a composed storybook I am unable to see the composed stories via MCP.

When running the same storybook locally with the same config, I am able to see the stories.

### Steps to reproduce the behavior

1. Use Storybook Composition to compose a chromatic hosted storybook

const config: StorybookConfig = { refs: { 'lib-b': { title: 'Lib B', url: 'https://main--b.chromatic.com', }, },

2. Set up MCP using the primary storybook

htt

[Read the thread](https://github.com/storybookjs/mcp/issues/305) · 2026-06-19 · open · external user · 2 comments

### [Bug] Declaring the dependency valibot with a caret

### Describe the bug

Is there any chance we can declare the dependency valibot with a caret(^). Because we met a peer dependency issue when trying to install storybook mcp and we pin the version of valibot

. └─┬ @storybook/addon-mcp 0.3.4 └─┬ @tmcp/adapter-valibot 0.1.5 └─┬ @valibot/to-json-schema 1.6.0 └── ✕ unmet peer valibot@^1.3.0: found 1.2.0 in @storybook/addon-mcp


### Steps to reproduce the behavior

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See

[Read the thread](https://github.com/storybookjs/mcp/issues/224) · 2026-05-11 · open · external user · 0 comments

### [Bug] subcomponent JSDocs & props are replaced by the parent's JSDocs & props

### Describe the bug
When using subcomponents (example: `<SegmentedControl.Button>`), the documentation in the manifest will completely replace any props or JSDocs you may have for the subcomponents with the docs & props for the parent component.

### Steps to reproduce the behavior

1. Add a tsx component `<Parent>` with JSDocs and props.
2. Add a child tsx component `<Child>` with JSDocs and props.
3. Assign the child to the parent as a subcomponent. `Parent.Child = Child`.
4. View the result 

[Read the thread](https://github.com/storybookjs/mcp/issues/216) · 2026-04-13 · open · external user · 1 comment

### Feature Request: Provide a more efficient way to search for components

### Problem
When instructing an agent to use for example a `button` component from storybook mcp, the agent will use the `get-documentation` tool with the `button` id.
This works for components that map their id exactly, but for components in folders, this will not work. If `button` is in a `general` folder, the id will be `general-button`, and the `get-documentation` will therefore fail to get the component.
The agent will then fallback to `list-all-documentation`, which might include hundreds 

[Read the thread](https://github.com/storybookjs/mcp/issues/215) · 2026-04-11 · open · external user · 1 comment

### MCP causing OOM during manifest generation and tool timeouts

I am facing two issues with `@storybook/addon-mcp`:

1. OOM at startup - The `componentsManifest` feature (enabled by default in Storybook 10.3, required by the addon) runs `react-docgen-typescript` across all components, causing "JavaScript heap out of memory" crashes at 32GB. The log shows "Experimental components manifest feature detected - registering component tools" right before the crash.
2. Tool timeouts - In the brief window where Storybook stayed alive (before OOM), `list-all-documenta

[Read the thread](https://github.com/storybookjs/mcp/issues/214) · 2026-04-08 · open · external user · 0 comments

### [Bug] createStorybookMcpHandler does not pass multiSource: true to tool registration when sources are configured

### Describe the bug

When using `createStorybookMcpHandler` with multiple `sources`, the `get-documentation` and `get-documentation-for-story` tools are registered **without** `{ multiSource: true }`. This causes a schema/validation mismatch:
 
1. The tool handler internally detects multiple sources and **requires** `storybookId`
2. But the tool's `inputSchema` does **not include** `storybookId` as a property
3. The transport layer (tmcp) strips unknown properties not present in the schema
4. `

[Read the thread](https://github.com/storybookjs/mcp/issues/213) · 2026-04-08 · open · external user · 2 comments

The remaining reports are on [the project's issue tracker](https://github.com/storybookjs/mcp/issues).