Built for agents

An agent that guesses component names and props writes code that doesn't compile. tealmac UI publishes its catalog in forms an agent can read, so it can look things up instead.

Three ways in

All three come from the same registry build, so they always agree.

What the MCP server returns

The hosted server answers with structured data, not prose:

• Categories and counts, so the agent knows what exists.
• Ranked search results with a short description of each item.
• Item details: description, props with types and defaults (read from the docs), dependencies, a usage example and the registry URL with the full source.
• The exact install command for the project's package manager.
• Quality rules: the accessibility and motion rules the library is built to, so the agent's own code meets the same bar.

The server is stateless and read-only. It never sees your code, and it never writes anything. Installing is still done by the CLI, in your project, when you or your agent run the command.

What llms.txt contains

/llms.txt lists every component with its one-line description and a link to its docs. /llms-full.txt adds the full source of each component and its examples, for agents that want to read everything in one request.

Tips for good results

• Ask for what you need, not for a component name: "a toast stack for upload progress" finds better matches than "toast".
• Let the agent call get_quality_rules before it writes UI.
• Review the diff. The agent installs real source into your repository, which is exactly what makes it easy to check.