Summary
Component code arrives with its size attached, so the context budget is a decision rather than a surprise.
Every fetch carries estimatedTokens, and the tools route around the heavy ones themselves: past 25000 tokens the instruction is to read the file list from get_component and pull files individually instead of taking the component whole. Nothing here writes into a project — it reads the library, its examples, and a cache you can clear by pattern when a listing goes stale.
What it is
A read-only catalogue over the UntitledUI component library, returning component source and page examples with an estimatedTokens figure attached to each response.
What you get
- Component categories listed — application, base, marketing and the rest — and the components inside one, with subfolders for variants such as modals under application
- Components searched by name across every category at once
- A component's code returned together with its file list and an estimatedTokens figure
- The same component with its base dependencies resolved, for when the imports are the point
- One named file out of a component, for when the whole thing is too large to take in a single response
- Whole page examples browsed by path and returned with all their files
Requirements
A license key that validate_license accepts. Nothing in the environment: no API key and no account named by any tool.
Setup effort
One command plus a key — npx untitledui-mcp, then supply credentials