Any plans for better component discovery / AI tooling support?

[ForrestCogna]

Hi Reshaped team — quick question from a team using Reshaped in a frontend codebase.

We’re thinking about some internal tooling to help developers and coding agents discover existing Reshaped components/patterns before building custom UI.

Before we go too far, I wanted to ask whether anything along those lines is already on your radar.

We took a quick look through the roadmap, issues, and docs/changelog, but didn’t spot anything obvious — though we may well have missed it.

Is there already any planned work around machine-readable docs, component discovery, or AI/tooling support for Reshaped?

Thanks!

[blvdmitry]

Hey @ForrestCogna, I do have plans for a "basic" mcp based on the docs but currently prioritizing the polish work for the v4 release. Besides typical library mcp for component discovery with docs and code examples for models to access, are there any other features you would be looking for?

[ForrestCogna]

That sounds like exactly the right scope. Component discovery with docs and code examples covers the core use case well.

One thing worth confirming as you spec it out: will prop types be included alongside the prose docs? That tends to be the detail that goes stale fastest in static documentation, so having it pulled from the actual installed version would make a meaningful difference for accuracy.

Looking forward to seeing it land after v4!

[blvdmitry]

btw, now that Storybook has released their MCP support publicly – that's what I've been exploring before in their early closed beta. They were using Reshaped to build the first version so I think it work to some extent already and the part I've been looking for is to also bring the docs source into the repo to provide it to the storybook mcp for more context about the component usage

Their release notes: https://storybook.js.org/blog/storybook-mcp-for-react/

[blvdmitry]

Just it a simple test in v4 branch with the latest storybook update: