Component Harvester 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_aceternity_componentC | Scans a specific Aceternity UI component page and stores the component. |
| list_harvested_componentsB | Lists components that have been harvested and stored. |
| get_aceternity_component_promptB | Retrieves a harvested Aceternity component and generates a detailed integration prompt. |
| scan_shadcn_componentB | Scans a specific shadcn UI component and stores it. |
| list_shadcn_componentsB | Lists all available shadcn UI components. |
| get_shadcn_component_promptB | Retrieves a harvested shadcn component and generates a detailed integration prompt. |
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 targets a distinct operation or component source (Aceternity vs shadcn). The list tools differentiate between all available components and those already harvested, preventing ambiguity.
All tools follow a consistent verb_noun pattern (scan_, get_, list_) using snake_case, making the tool surface predictable and easy to navigate.
6 tools is well-suited for a focused server handling two component libraries, covering scanning, retrieval with prompts, and listing without unnecessary bloat.
The tool set covers the main lifecycle (scan, list, retrieve) but lacks update or delete operations. This minor gap does not hinder the core harvesting workflow.