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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_componentA | 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_categoryA | 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
Each tool has a fairly clear purpose, but three tools (list_components, get_category, search_components) all act as discovery entry points and could be confused by an agent. get_component vs get_usage is also a mild overlap since both take a component and return related content (markup vs docs).
All seven names follow a strict snake_case verb_noun pattern (get_*, list_*, search_*). The verbs map predictably to the return shape, making the set easy to scan.
Seven tools is well-scoped for a component-library documentation server; each tool covers a distinct facet (code, docs, setup, theming, discovery). Nothing feels padded or missing at the count level.
The surface covers discovery, component markup, usage docs, CSS setup, and theme script, which is solid for a UI library. Minor gaps: no way to retrieve full example pages or framework-specific snippets, and category listing partially duplicates list_components.