AI Canvas
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | Return every category in the AI Canvas standalone component library, with the number of components in each. Use to orient before listing or searching — e.g. "what kinds of components are available?" |
| list_componentsA | Return AI Canvas components, optionally filtered by category. Use after |
| search_componentsA | Fuzzy keyword search across component slug, name, description, categories, and tags. Returns best matches ranked by relevance. Use when the user describes what they want in their own words, e.g. "an animated card stack", "background with waves", "typography that reveals on scroll". Results include screenshot URLs and install commands for immediate evaluation. |
| get_componentA | Return the complete record for a single component: metadata + the entire .tsx source code as a string. Use after the user picks one from a search/list result and wants to see the implementation, or before installing if they want to inspect first. The source is the exact file the CLI install would write into a project. |
| get_install_commandA | Return the shadcn CLI command to install a single component into the user's project. After calling this, suggest the user run the command (or run it yourself if you have shell access). Requires shadcn-aware setup (Tailwind v4, components.json) — for projects without that, fall back to |
| list_systemsA | Return every design system available on AI Canvas. A design system is a coordinated set of components plus shared tokens and utilities — installable in one CLI command. Use when the user asks about "themes", "design systems", or wants more than a single component. |
| get_systemA | Return all files for a design system in a single response — every component, plus shared tokens and utilities — ready to write into the user's project. Use when the user wants to adopt a whole system rather than pick individual components. |
| list_templatesA | Return every ready-made template on AI Canvas. A template is a complete example screen built from one design system — a dashboard, a console, a control room — installable in one CLI command. Use to discover what full screens exist before fetching one with |
| get_templateA | Return all files for a single template — the example composition plus every component it uses plus shared tokens. Use for "I want exactly this dashboard" / "give me the entire mission-control screen". One CLI command installs all files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: categories, components, systems, and templates are clearly separated, and list/search/get/install roles are easy to tell apart. The descriptions reinforce the intended workflow without meaningful overlap.
Tool names follow a consistent verb_noun pattern: list_* for plural collections, get_* for single resources, and search_components for the one search entry point. This makes the API predictable and easy to navigate.
Nine tools is well-scoped for a component/design-system registry. Each tool covers a clear part of the discovery-to-install workflow, and none feel redundant or unnecessary.
The main workflows are covered: browse categories, list/search components, inspect source, get install commands, and retrieve full systems or templates. Minor gaps exist around searching systems/templates by keyword and obtaining install commands for full systems, but these are not blocking.