coss-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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| coss_list_componentsA | List the coss ui catalog (components, hooks, or overview docs) with one-line descriptions. Cheap overview — call before fetching full docs. |
| coss_searchA | Search coss ui components/hooks by name, keyword, or use case (e.g. "date range picker", "toast notification"). Returns ranked matches with install commands. Use first to find the right component. |
| coss_get_componentA | Get the full docs for ONE coss ui component or hook: install (shadcn CLI + manual npm deps + CSS tokens), usage, full API/props reference, and examples. Fetch on demand after search/plan. |
| coss_get_docA | Get an overview/guide doc: introduction, get-started, styling, or roadmap. |
| coss_themeA | Get coss ui's design-token + font conventions and setup commands — the shadcn-style CSS variables (colors, sidebar, --info/--success/--warning/--destructive-foreground), font tokens, and the full @theme block. Use when setting up a project or rebranding the look. Pass format:"full" for the complete styling guide. |
| coss_planA | Given a natural-language description of a screen or feature, return the recommended coss ui components (ranked, with install commands) plus base project setup. The token-efficient starting point — call this first, then coss_get_component for the ones you'll build with. |
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 6 tools
Each tool has a clearly distinct purpose: listing all components, searching for specific ones, getting detailed docs for a component, getting overview docs, planning a UI with recommendations, and fetching theme info. No overlap in functionality, and descriptions guide appropriate use.
Tools follow a 'coss_<verb>_<noun>' pattern for most (get_component, get_doc, list_components), but three tools use a single verb without a noun (plan, search, theme). While readable and prefixed consistently, the lack of uniform verb-noun structure slightly reduces predictability.
With 6 tools covering exploration, search, detailed documentation, planning, and theming, the count is well-scoped for a UI component library reference server. Each tool provides essential functionality without unnecessary redundancy.
The tool set covers the full lifecycle of using the component library: discovering (list, search), understanding (get_component, get_doc), planning (plan), and styling (theme). No obvious gaps for a read-only reference MCP server.