Basecoat UI MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_componentC | Get HTML code for a specific Basecoat component |
| list_componentsB | List all available Basecoat components organized by category |
| get_usageC | Get usage documentation for a component |
| get_setupB | Get Basecoat CSS setup code with CDN links |
| get_theme_scriptB | Get theme switcher script for dark/light mode |
| search_componentsC | Search for components by name or category |
| get_categoryC | Get all components in a specific category |
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 7 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, get_component retrieves HTML code, get_usage provides documentation, and list_components organizes components by category. The descriptions make it easy to differentiate between tools like get_category (components in a category) and search_components (search by name/category).
All tool names follow a consistent verb_noun pattern with snake_case, such as get_category, list_components, and search_components. The verbs (get, list, search) are used appropriately and predictably across the set, making the naming scheme highly readable and uniform.
With 7 tools, the count is well-scoped for a UI component library server, covering core operations like listing, searching, retrieving code, and documentation. Each tool earns its place without feeling excessive or insufficient, providing a balanced surface for interacting with Basecoat components.
The tool set offers strong coverage for retrieving and exploring Basecoat components, including setup, themes, and usage. A minor gap exists in lacking update or customization tools (e.g., modify components), but agents can work around this as the server focuses on read-only access to a static library.