Improve Storybook MCP docs for monorepos with package-scoped Storybook setups #35307
Replies: 1 comment
-
|
The docs improvement I would make is to separate dependency placement from runtime working directory. For monorepos, the important runtime rule is: start Storybook from the package/context that owns the Depending on the package manager, A docs example like this would cover the common case: pnpm --filter <storybook-package> storybookThen configure the client with the actual port printed by that Storybook process. That would also explain why running from the repo root can fail when Vite config paths are package-relative. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m trying to set up Storybook MCP in a monorepo where Storybook runs from a package subdirectory rather than the repository root. The current documentation assumes a simpler setup and doesn’t clearly cover monorepo-specific installation and startup steps, which makes it harder to configure the addon correctly and connect the MCP endpoint from local tools such as VS Code.
During setup, we ran into a few issues that seem relevant to other monorepo users as well:
It would be helpful if the docs included guidance for:
Beta Was this translation helpful? Give feedback.
All reactions