component-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | Scans the contexts/ directory and returns the names of all available design system components (without the .md extension), so a caller can discover what's available before requesting details. |
| get_component_contextA | Looks up contexts/.md (case-insensitive) and returns its parsed frontmatter, raw markdown body, and full raw file content. If the component isn't found, returns an error listing the currently available component names. |
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 2 tools
The two tools have clearly distinct purposes: one lists available components, the other retrieves detailed content for a specific component. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern with snake_case (list_components, get_component_context), making the naming predictable and clear.
With only two tools, the server feels minimal but still covers basic discovery and retrieval. However, for a server named 'component-mcp-server', a few more tools (e.g., search or create) might be expected, so the count is borderline.
The server only supports reading components (list and get). Missing create, update, and delete operations leave significant gaps for full component lifecycle management, limiting its usefulness for agents needing to modify components.