mcp-react-component-harvester

This MCP server acts as a component harvester for React UI libraries, focusing on Aceternity UI and Shadcn UI. It discovers available components by querying the official registries, stores full component data for Aceternity components (including code and dependencies), and stores metadata for Shadcn components (metadata such as dependencies and file lists). It maintains a central index of harvested components and provides integration prompts that guide you on how to use or integrate each component into a project. You can use the provided tools to list harvested components, scan specific components, and generate step-by-step integration prompts tailored to either Aceternity UI (full code and dependencies) or Shadcn UI (CLI-based guidance).

Prerequisites:

• Node.js installed (version 14+ recommended)
• Git installed
• Internet access to fetch registries

Install steps:

1. Clone the repository or download the MCP server package.
2. Install dependencies (if a package.json is provided) with: npm install
3. Configure environment variables (see mcp_config env hints below) and ensure registry URLs are reachable:
   • ACETERNITY_REGISTRY_URL or default https://ui.aceternity.com/registry
   • SHADCN_REGISTRY_URL or default https://ui.shadcn.com/registry
4. Start the server with the appropriate command for your setup. Example (adjust path to your server entry file): node path/to/server.js
5. Interact with the available endpoints/tools to list harvested components, scan for specific components, and generate integration prompts.

Note: If you prefer using a container or a different runtime, you can adapt the mcp_config to your environment (see Additional Notes for guidance).

Notes and tips:

• The server stores harvested data under data/aceternity/ and data/shadcn/, with an index at data/harvested_index.json. Ensure these paths exist and are writable.
• The Aceternity UI harvests include full component JSON (code, dependencies, file structure). Shadcn harvests store metadata (deps, file lists) since full source code is not provided by Shadcn’s registry.
• Use the list_harvested_components tool to get an overview of available components. Use scan_aceternity_component or scan_shadcn_component to fetch or refresh data for a given component name.
• When generating integration prompts, the Aceternity prompts include complete code and file paths for manual integration, while Shadcn prompts guide using the CLI (npx shadcn-ui@latest add [slug]) and enumerate expected files and dependencies.
• If registry URLs become unavailable, consider temporarily hosting mirrors or local fallbacks and updating the environment variables accordingly.
• For troubleshooting, check data/harvested_index.json consistency and ensure there are no permission issues writing to the data directories.