OriginUI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_componentsC | Search OriginUI components by name, category, or tags |
| get_component_detailsB | Get detailed information about a specific OriginUI component |
| list_componentsB | List all available OriginUI components with basic information |
| get_install_commandB | Get the installation command for a specific component |
| get_component_previewC | Get component preview information including styling and usage |
| get_component_screenshotC | Get component screenshot/visual preview to help assess if it fits the project |
| get_registry_statsB | Get comprehensive statistics about the OriginUI component registry |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose with no ambiguity: list_components and search_components handle discovery, get_component_details/preview/screenshot provide different types of component information, get_install_command gives installation instructions, and get_registry_stats offers registry-level data. The descriptions make it easy to differentiate between tools like get_component_details (detailed info) and get_component_preview (styling/usage).
All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., get_component_details, list_components, search_components). The naming is predictable and readable, using clear verbs like 'get', 'list', and 'search' consistently across the toolset.
With 7 tools, this server is well-scoped for its purpose of managing a UI component registry. Each tool earns its place by covering distinct aspects: discovery (list/search), component inspection (details/preview/screenshot), installation (install_command), and registry analytics (stats). This count is neither too thin nor overwhelming.
The tool surface provides comprehensive coverage for the domain of a UI component registry, including discovery, inspection, and installation. Minor gaps exist, such as no tools for managing components (e.g., create/update/delete) or user-specific actions (e.g., favorites), but agents can work around this for core workflows like finding and using components.