basecoat-ui
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASECOAT_PROJECT_ROOT | No | Overrides the launch directory to select the host application's DESIGN.md. It is not the MCP installation directory. This is overridden by --project-root. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_componentsA | Find up to 8 compact component summaries by intent and query. No matches returns an empty list; no markup is returned. |
| get_component_detailsA | Get one minimal component template, dependencies, and composition tips for Astro or HTML. Response is bounded below 2000 UTF-8 bytes. |
| validate_compositionA | Statically check HTML/Astro source for Basecoat migration errors, missing scripts, nested cards, spacing and hierarchy issues. Include layout imports. Does not render or evaluate dynamic code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| design-rhythm | Content hierarchy, spatial rhythm, density, typography, and composition constraints. |
| astro-integration | Production Astro/Vite/Tailwind 4 setup, selective JS, native dialog and prototype distinction. |
| project-context | Read DESIGN.md from the explicitly configured host project root; bounded local data. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: searching, retrieving details, and validating composition. No two tools overlap in functionality, so agents can easily select the correct one.
All tool names follow a consistent verb + noun pattern (search_components, get_component_details, validate_composition). The verbs describe the exact action and the nouns indicate the target resource, making the pattern predictable.
Three tools is well-scoped for a read-only component reference server. Each tool addresses a core need—discovery, deep detail, and safety validation—without unnecessary bloat.
The server covers the full arc of a component reference workflow: search to find components, get details to use them, and validate to ensure correct integration. No obvious operations are missing for its stated purpose.