Summary
The choice between three similar components can be made in the editor, screenshot included.
Everything past discovery is keyed on componentId, so search_components or list_components is always the first call. get_component_screenshot takes a theme argument, which is what makes it useful for the judgement it is meant for — a component that looks right in light and wrong in dark. get_install_command returns the command for that one component rather than for the library.
What it is
An OriginUI registry client covering 7 tools, over component metadata, previews and install commands.
What you get
- Finding the candidates: search_components queries by name, category or tag with a limit, and list_components returns the registry with basic information per component.
- Judging one before adopting it: get_component_details returns the detail for a componentId, get_component_preview returns styling and usage, and get_component_screenshot renders it in a chosen theme.
- Getting it into the project: get_install_command returns the installation command for a specific componentId.
- Sizing up the registry itself through get_registry_stats.
Requirements
No account and no key; every call after the first search is addressed by componentId.
Setup effort
One command — npx --yes github:kelvinchng/origin-ui-mcp