Built for AI agents

Every Ballmac item includes a description written for agents, when to use it and when not to, the items it composes with, keyboard notes and working examples. An agent can pick the right component and wire it up correctly, instead of guessing from a name.

Three ways in

• The Ballmac MCP server. @ballmac/mcp searches the catalog, reads props and examples, returns install commands, and plans pages from blocks. Connect it.
• The shadcn MCP server. It lists, searches and views registry items and gets the add command. Use it.
• No MCP. Point any assistant at ui.ballmac.com/llms.txt, which lists every component with its purpose and install command, or at llms-full.txt for the documentation in one file. Every docs page is also available as Markdown: add /md in front of the address and .md at the end, for example /md/docs/get-started/install.md.

A gate before the agent finishes

get_quality_rules lets an agent read the rules before it writes a component, and audit_project runs the same check as ballmac check on its work. Tell the agent to run it before it says it is done.

Want this for your own design system?

We build private, shadcn-compatible registries with an MCP server for teams, so their AI coding agents use their own components. See how it works and what it costs.