Support for Development/Testing tools in remote @storybook/mcp setups

[k35o]

I am exploring a remote/self-hosted @storybook/mcp setup for our workflow, and it seems to work well for documentation lookup.

However, in testing this setup, I noticed a functional gap:

Docs-related tools are available via @storybook/mcp.

Development/Testing tools appear to live in @storybook/addon-mcp and are only available when running inside a Storybook instance.

This creates a limitation for remote/centralized MCP setups. While agents can access documentation, they are unable to leverage development or testing workflows.

Questions:

• Is this separation an intentional long-term design boundary?
• Is there a plan to make some of the Development/Testing tools available in remote/self-hosted MCP setups as well?

My ideal use case is to expose Storybook over MCP remotely, allowing agents to do more than just documentation lookup when appropriate.

If there are no plans to support this in @storybook/mcp, I would appreciate any recommendations on the best architecture for a remote setup that requires more than just docs tooling.