get_component_details
Get detailed information about a specific OriginUI component
LABSCO 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
USE CASES
01
Choosing between three similar components without opening a gallery
Search the registry, read what each candidate is, and look at it rendered in the theme your app ships in.
02
Getting the component you picked into the project
Check its styling and usage first, then take the install command for that specific component.
03
Sizing up a registry before you build on it
List what is there and read the registry's own statistics rather than judging it from the handful of components search returned.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_component_preview
Get component preview information including styling and usage
get_component_screenshot
Get component screenshot/visual preview to help assess if it fits the project
get_install_command
Get the installation command for a specific component
get_registry_stats
Get comprehensive statistics about the OriginUI component registry
list_components
List all available OriginUI components with basic information
search_components
Search OriginUI components by name, category, or tags
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"origin-ui-mcp": {
"command": "npx",
"args": [
"--yes",
"github:kelvinchng/origin-ui-mcp"
]
}
}
}npx
TERMINAL
npx --yes github:kelvinchng/origin-ui-mcp
