MCP integrations
Use Storybook context and Compify registry context without conflating their roles.
There are upstream and downstream MCP surfaces with different authority:
- The official Storybook MCP server exposes a project's Storybook context to agents. Its MCP/manifests path is currently preview/unstable and React-only. Storybook remains upstream for authoring, tests, and docs.
- The official shadcn MCP consumes registries configured in the target
project's
components.jsonand owns discovery/installation semantics. compify mcpis a deprecated compatibility registry browser. It does not inspect local Storybook source or add approval/provenance evidence beyond the item itself. Do not build new integrations around it; it may be removed unless pilots prove a Compify-specific evidence tool is needed.
Static compify storybook inspect and export do not require either server.
Preferred downstream integration
Configure the Compify namespace (including optional Bearer headers) as shown in Registry, then follow the official shadcn MCP documentation. This preserves native alias, target, dependency and authentication behavior.
Deprecated Compify registry MCP
Build and link the current CLI source, then register its linked stdio executable with your MCP client:
{
"mcpServers": {
"compify": {
"command": "compify",
"args": ["mcp"]
}
}
}The MCP client must inherit the path containing the linked executable. The only
published CLI, @compify/cli@0.1.0, does not contain this compatibility server;
use the built 0.2.0 source candidate until publication is explicitly
announced. A manifest version is not a release.
Compatibility tools
| Tool | What it does |
|---|---|
search_components | Search public registry metadata and return addresses and preview links |
get_component | Return source files and package dependencies in registry-item form |
get_install_commands | Return Bun-based shadcn and Compify install commands |
Official Storybook MCP
Follow Storybook's official MCP documentation for setup compatible with your Storybook version. As of the evidence review, the official MCP integration and component manifests are preview/unstable and React-only; do not treat their current protocol or output as a stable cross-renderer contract. Use the integration when an agent needs the stories, docs, or component-development context already maintained there. Use Compify translation separately when you want a selected, reviewable registry artifact.
If a project configures a Compify namespace in components.json, the official
shadcn MCP can also work with registry items through that namespace. That is a
third integration path and does not make Compify a Storybook MCP implementation.