Component Library MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRAMEWORK | No | react | vue | auto. Auto detects from package.json deps. | auto |
| LOG_LEVEL | No | silent | info | debug. All logs go to stderr. | silent |
| MAX_DEPTH | No | Max recursion depth for fast-glob. | 10 |
| PROJECT_ROOT | No | Absolute path to scan. Usually you don't need to set this — the server uses the directory it was launched from. Only set it when that isn't what you want. | |
| COMPONENT_DIRS | No | Comma-separated dirs to scan. 'auto' probes src/components, src/ui, src/shared, components, lib/components, app/components and falls back to src/ or the project root. | auto |
| INCLUDE_STORIES | No | Parse .stories.(ts|tsx|js|jsx) and attach story examples to components. | true |
| EXCLUDE_PATTERNS | No | Comma-separated dir names or globs. Bare names become **/<name>/**. | node_modules,dist,.next,.nuxt |
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_componentsC | List all components in the project with summary info (name, path, prop count, usage count). Call this first to see what's available. |
| get_component_detailsA | Get full metadata for a specific component: props, slots, events, description, and story examples. Accepts component name or file_path. |
| search_componentsA | Search components by natural-language query, prop name, prop type, or slot name. Returns ranked results. |
| get_import_graphC | Get dependencies and dependents for a component. Shows composition patterns and which pages/components use it. |
| check_duplicateA | Check if a proposed component would duplicate an existing one. Call this BEFORE creating a new component. Returns similarity-ranked matches and a recommendation. |
| get_component_usage_exampleC | Get real usage examples of a component from the codebase (JSX/template snippets with surrounding context). |
| refresh_cacheA | Force re-scan of all component files. Incremental by default; pass full_scan=true to clear the cache entirely. |
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 distinct purpose: checking duplicates, getting details, usage examples, import graph, listing, refreshing cache, and searching. No overlap, clear boundaries.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_duplicate, list_components, refresh_cache), making them predictable and readable.
Seven tools cover the essential operations for a component library: discovery, inspection, dependency analysis, and cache management. The scope is well-balanced, neither too sparse nor excessive.
The tool surface covers querying and analysis well (list, search, details, examples, dependencies) but lacks any creation or modification tools, which is a notable gap given the server's domain.