`get_component_props` returns the real TypeScript interfaces and `get_component_examples` returns the co-located .demo.tsx usage, so the agent copies a call that already works rather than reconstructing one. `get_component_dependencies` is the quiet complement, surfacing the internal imports a component needs before you paste it somewhere that lacks them, and nothing here writes into your project, so the last step stays yours.
A source-of-truth server for the Untitled UI component library: 9 tools that search components and icons and return a component's full source, its props, its internal dependencies, its usage examples and the official CLI command that installs it.
- Two ways in depending on what you already know: `search_components` fuzzy-matches on name, category, subcategory or export name under a `limit`, and `list_components` enumerates a `category` optionally narrowed by `subcategory`.
- The component itself rather than a description of it: `get_component` returns full source by `name` and `get_component_file` returns it by relative `path`.
- The contract before the implementation: `get_component_props` returns the TypeScript props and interfaces declared for a component.
- What a component brings with it: `get_component_dependencies` shows the internal Untitled UI imports it uses, which is what decides whether pasting it into a file compiles.
- Working examples instead of invented ones: `get_component_examples` returns usage drawn from the co-located .demo.tsx files.
- Icons searchable by name: `search_icons` matches Untitled UI icon names under a `limit`.
- The vendor's own install path: `get_install_command` returns the official Untitled UI CLI command for a component, documented as pulling in the required dependencies itself.
No account and no key. The tools read the Untitled UI library, so what they return lands in a project already using it, and `get_install_command` returns the vendor's CLI invocation rather than executing anything on your behalf.
One command — npx -y mcp-server-untitled-ui