local-component-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_componentsC | Search for Vue components (.vue files) in a specified local directory workspace. |
| get_component_detailB | Parse a Vue component file to extract its Props, Events, Slots, and other metadata. |
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
Both tools have clearly distinct purposes: one searches for component files, the other parses a specific component's metadata. No overlap in functionality.
Both tool names follow a consistent verb_noun pattern (get_component_detail, search_components), making it easy to predict their actions.
With only 2 tools, the server feels minimal. While they cover basic search and detail retrieval, the scope is thin for a component management server.
The server lacks essential operations for a complete component workflow, such as listing all components, creating, updating, or deleting. Users can only search and get details, which is a notable gap.