ballmac-ui-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_itemsA | List components, blocks or templates, optionally filtered by kind, category (a component category such as primitives, motion or ai; a block section such as hero or pricing; or a template kind such as marketing) or tier. Call list_categories for the valid names. |
| list_categoriesA | How many components, blocks and templates there are, and the categories each is grouped into, with counts. Use the names as the category filter of list_items. |
| search_itemsA | Search by what the user needs (for example 'chat input with attachments', 'animated stat', 'pricing section', 'online store'). Understands common synonyms such as modal, navbar or ecommerce. Returns the best matches with when-to-use guidance. |
| get_itemA | Everything about one item: description, when to use and not, import line, props, keyboard behaviour, dependencies, composition hints, template pages and the full source (for Pro items only when the server has BALLMAC_LICENSE_KEY; see the |
| get_examplesB | Working example code for an item (the same examples shown on its page). |
| get_install_commandA | The shadcn CLI commands to add one or more items to the user's project. Run |
| compose_pageB | Plan a page from Ballmac UI blocks for an intent such as 'SaaS landing page with pricing and FAQ' or 'login screen'. Returns the chosen blocks in page order, install commands, a page.tsx scaffold that renders them, and any complete templates that already fit the intent. |
| get_setupB | How to prepare a project for Ballmac UI (shadcn init, registry entry, optional theme) and its requirements. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_page | Plan and build a page from Ballmac UI blocks, or start from a template that fits. |
| choose_component | Find the right component for a need and wire it up correctly. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | Every component, block and template with a one-line description. |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes (list_items vs get_item vs compose_page). The only mild overlap is between list_items, list_categories, and search_items, plus get_item vs get_examples, but the descriptions clarify the boundaries (browse vs filter-by-category vs need-based search, full detail vs examples only).
All eight tools follow a consistent snake_case verb_noun pattern (get_examples, list_items, list_categories, search_items, get_item, get_install_command, compose_page, get_setup). No mixed conventions or vague verbs.
Eight tools is well-scoped for a UI component registry, covering discovery, detail, install and composition without bloat. Each tool earns its place.
The surface covers discovery (list/search/categories), inspection (get_item/get_examples), setup, install and page composition—a coherent read-only lifecycle for a component catalog. Minor gaps like versioning or license-status checks exist but are workable.