Coding agents write better UI when they can look things up instead of guessing. tealmac UI runs a hosted MCP server that lets an agent search the catalog, read an item's props and usage, and get the exact install command. There is no account and no key.
https://ui.tealmac.com/mcpMost clients read a JSON file with an mcpServers object. Add one entry:
{
"mcpServers": {
"tealmac-ui": {
"url": "https://ui.tealmac.com/mcp"
}
}
}The file name and key differ slightly between clients:
Put the snippet above in .cursor/mcp.json in your project, or in
~/.cursor/mcp.json to use it everywhere.
Reload the client. It should list six tools:
| Tool | What it does |
|---|---|
list_categories | Categories with item counts |
search_items | Ranked search by need, optionally limited to one type |
list_items | Every item, optionally in one category or of one type |
get_item | Description, props, usage, dependencies and the source URL |
get_install_command | The exact CLI command, for npm, pnpm, yarn or bun |
get_quality_rules | The accessibility and motion rules to build to |
The MCP tools reference lists every input and the shape of each answer.
For example:
tealmac UI is a standard shadcn registry, so the official shadcn MCP server
works too. Register the namespace in components.json:
{
"registries": {
"@tealmac": "https://ui.tealmac.com/r/{name}.json"
}
}Then let the CLI write the client configuration for you:
pnpm dlx shadcn@latest mcp init --client cursor
--client also accepts vscode, codex and opencode.
Agents that can fetch URLs can read the catalog as plain text:
/llms.txt: every component with a
one-line description and a link./llms-full.txt: the same list with
each component's full source and examples./r/registry.json: the registry
index in shadcn format.Read Built for agents for how these fit together.