mcp-react-component-harvester

The Component Harvester MCP Server is a tool that automates the process of finding, fetching, and integrating React components from popular UI libraries. It supports both direct code harvesting and CLI-based integration guidance. The server fetches component information from Aceternity UI and Shadcn UI, storing this information to generate detailed prompts for AI agents or developers to integrate these components into their projects. For Aceternity UI, it retrieves full component code and dependencies, while for Shadcn UI, it provides metadata and CLI-based integration instructions. The server maintains a central index of all processed components and can generate integration blueprints for manual or CLI-based integration.

Features

• {'name': 'Discover Components', 'description': 'Automatically learns about available components by fetching and parsing JSON registries from Aceternity UI and Shadcn UI.'}
• {'name': 'Fetch Component Data', 'description': 'Retrieves detailed JSON data for Aceternity UI components and metadata for Shadcn UI components.'}
• {'name': 'Store Locally', 'description': 'Maintains a central index and stores detailed data for each component in source-specific directories.'}
• {'name': 'Generate Integration Blueprints', 'description': 'Produces detailed prompts for integrating components, including full code and CLI instructions.'}

MCP Tools

• list_harvested_components: Lists all components stored in the index.
• scan_aceternity_component: Fetches and stores full data for an Aceternity UI component.
• get_aceternity_component_prompt: Generates a detailed integration guide for a scanned Aceternity UI component.
• list_shadcn_components: Lists all components available in the Shadcn UI registry cache.
• scan_shadcn_component: Processes and stores metadata for a Shadcn UI component from its main registry.
• get_shadcn_component_prompt: Generates an integration guide for a Shadcn UI component.

Usage with Different Platforms

mcp

mermaid
graph TD
    subgraph Server Startup
        direction LR
        A1[Initiate] --> A2a[Fetch JSON from aceternity.com/registry]
        A2a --> A3a[Parse Aceternity JSON & Cache Slugs]
        A1 --> A2b[Fetch JSON from shadcn.com/registry]
        A2b --> A3b[Parse Shadcn JSON & Cache Metadata]
    end
    A3a --> A4[Server Ready]
    A3b --> A4