Replies: 1 comment
-
|
I’ve built a custom registry that already includes all of the default shadcn components, along with a few internal tweaks specific to our team’s design system. Having both the default registry and our custom one show up side by side feels a bit redundant and it can easily confuse less technical team members who might accidentally install components from the wrong source. It would be great if there were a way to disable or override the default registry entirely, so that only our custom registry appears within the MCP environment. Is there a supported flag or configuration option for this, or would I need to modify the registry loading logic manually? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I was wondering if it was possible to not include the default shadcn registry in the MCP server. I have built a custom registry using all the default shadcn components, so it is kinda redundant ( and potentially confusing) to have the default option available. This would make it easier for less technical team members to not get confused and install the wrong components.
Beta Was this translation helpful? Give feedback.
All reactions