Storybook context, approved source, native installation

Agent access to component documentation is not authorization to distribute source. A trustworthy workflow keeps three responsibilities separate.

1. Storybook owns understanding and tests

The official Storybook MCP/tools expose docs, stories, previews and tests. Its React manifests and MCP APIs are still moving quickly. Compify does not proxy or reproduce them.

2. Compify owns explicit source review

A maintainer selects a local CSF boundary. The CLI statically analyzes the component graph without executing the story, reports unsupported behavior, and emits reviewable registry JSON with a digest and provenance.

compify storybook inspect src/Button.stories.tsx --story Primary

3. shadcn owns installation

Configure the registry in components.json, then use the official shadcn CLI or MCP so target aliases, dependencies and authentication follow native semantics.

"registries": { "@compify": "https://registry.example/r/{name}.json" }

The existing compify mcp registry browser is deprecated compatibility surface. The useful future agent capability is approval and verification evidence—not another raw component search tool or an automatic publish button.