design-system-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_componentB | Returns design system component info by exact name |
| find_component_for_use_caseB | Finds the most relevant design system component based on a use case description |
| list_components_by_categoryB | Lists all available components optionally filtered by 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 3 tools
Each tool has a clearly distinct purpose: retrieving by exact name, finding by use case description, and listing by category. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (get, find, list) with descriptive objects, and all use snake_case. The naming is predictable and uniform.
Three tools is well-scoped for a read-only design system lookup server. Each tool covers a distinct query need without unnecessary bloat.
The tool set covers the main discovery operations: exact lookup, use-case-based search, and listing by category. Minor gaps like direct search by keyword or component versioning could exist, but the core surface is complete for typical usage.