Include MDX documentation in MCP server

[TheSonOfThomp]

Summary

Not sure if I'm missing something, or if it's not currently possible.

I have *.stories.tsx files for my main stories, and those are picked up just fine in the component manifest, and served on the MCP. I also have *.docs.mdx for custom documentation (pattern is defined in main.ts), but the "prose" docs are not being picked up by the MCP tools.

Is this a configuration thing on my side, or is this not yet possible in the Storybook MCP?

EDIT: Resolved

I was running @storybook/addon-mcp@0.2.2, and this was fixed in 0.2.3. Updating to latest resolved the issue

[dosubot[bot]]

Hi @TheSonOfThomp! I'm Dosu and I’m helping the storybook team.

MDX documentation is supported in the Storybook MCP server. Your *.docs.mdx files should be picked up automatically, so this is likely a configuration issue.

Most common cause: Your MDX files need to match the stories glob pattern in your main.ts. Try updating it to include .mdx files:

stories: [
  '../src/**/*.mdx',
  '../src/**/*.stories.tsx',
],

How MDX appears in MCP:

• Attached MDX (uses <Meta of={ComponentStories} />) → appears in /manifests/components.json under the component's docs property
• Unattached MDX (standalone docs without <Meta of={...} />) → appears in /manifests/docs.json

To debug, check the manifest endpoints directly while Storybook is running:

• http://localhost:6006/manifests/components.json
• http://localhost:6006/manifests/docs.json

If your MDX files aren't showing in either manifest, the issue is in the stories glob pattern. Could you share your current stories config from main.ts?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[TheSonOfThomp]

@dosu
I do have the glob pattern set in main.ts, with experimentalComponentsManifest enabled.

  stories: [
    '../packages/components/src/**/*.docs.@(mdx)',
    '../packages/components/src/**/*.stories.@(ts|tsx)',
  ],
  features: {
    experimentalComponentsManifest: true,
  },

The page does render in the Storybook UI.

I also have <Meta /> defined in my .mdx file:

import { Canvas, Controls, Meta } from '@storybook/addon-docs/blocks';

import * as BadgeStories from './Badge.stories';

<Meta of={BadgeStories} />

The docs appear in manifest/components.json, but not manifest/docs.json

[dosubot[bot]]

That's the expected behavior. Since you're using <Meta of={BadgeStories} />, your MDX file is attached to the Badge component, so it appears in components.json under the component's docs property — not in docs.json.

The docs.json manifest is only for unattached standalone docs (MDX files without a <Meta of={...} /> reference).

Your attached MDX content should be nested within the component entry in components.json like this:

{
  "components": {
    "badge": {
      "docs": {
        "badge--docs": {
          "content": "Your full MDX prose content here..."
        }
      }
    }
  }
}

Could you check if the docs property within your Badge component entry in components.json includes a content field with your full MDX text? If it's there, the MCP tools should be able to access it.

If the content is present in the manifest but not being returned by specific MCP tools, that could indicate an issue with how those tools traverse the nested structure. Which MCP tool are you using that isn't showing the documentation?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[TheSonOfThomp]

@dosu
Docs are available for badge.

{
  "components": {
    "components-badge": {
      "docs": {
        "components-badge--docs": {
          "content": "Your full MDX prose content here..."
        }
      }
    }
  }
}

However the MCP only returns basic documentation, without the MDX:

{
content: [
  0: {
    type: "text"
    text: "# Badge ID: components-badge ## Stories ### Default ``` import { Badge } from "../components"; const Default = () => <Badge variant={BadgeVariant.LightGray}>Badge</Badge>; ```"
    }
  ]
}

[dosubot[bot]]

Thanks for confirming. Your manifest generation is working correctly — the MDX content is present in components.json. The issue appears to be in the MCP get-documentation tool implementation itself, which isn't returning the attached docs.content field.

The documentation states that get-documentation should return "any additional documentation you've provided," but it seems the tool is currently only returning component metadata and story snippets, not the MDX prose content.

The MCP tools are implemented in a separate repository (storybookjs/mcp), so this looks like either a bug or missing feature in that package. I'd suggest opening an issue there describing exactly what you've shown here — that the MDX content exists in the manifest but isn't being surfaced through the tool response. This would be valuable feedback for the maintainers.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}