MCP.so
ログイン

Component Harvester MCP Server ✨

@dazeb

Component Harvester MCP Server ✨ について

A Model Context Protocol (MCP) server that automatically discovers, fetches and processes react components from popular react libraries like Aceternity and Shadcn

基本情報

カテゴリ

その他

ランタイム

html

トランスポート

stdio

公開者

dazeb

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Component Harvester MCP Server?

An MCP server that acts as an AI agent’s assistant for sourcing React components from popular UI libraries. It automates discovering, fetching, and generating integration guidance for components from Aceternity UI and Shadcn UI.

How to use Component Harvester MCP Server?

Invoke the server’s MCP tools to scan components, list harvested components, and generate integration prompts. Use commands like scan_aceternity_component, get_aceternity_component_prompt, scan_shadcn_component, get_shadcn_component_prompt, and list_harvested_components.

Key features of Component Harvester MCP Server

  • Fetches full component code from Aceternity UI
  • Retrieves metadata and CLI guidance for Shadcn UI
  • Stores component data locally in structured JSON files
  • Maintains a central index of all harvested components
  • Generates detailed, step‑by‑step integration blueprints
  • Caches registry data for fast lookups

Use cases of Component Harvester MCP Server

  • Automatically fetch the code and dependencies for an Aceternity UI “3D Pin” component
  • Get CLI installation instructions for a Shadcn UI “Alert Dialog” component
  • List all available components from Aceternity or Shadcn to plan a project
  • Generate a full integration guide for a set of React components

FAQ from Component Harvester MCP Server

Which UI libraries are supported?

Aceternity UI and Shadcn UI are currently supported, with more planned.

Does the server fetch full source code for Shadcn components?

No, for Shadcn UI only metadata (dependencies, file list) is retrieved; full source code is not provided because Shadcn components are added via CLI.

Where does the server store harvested data?

Data is stored locally in a data/ directory: a central index (data/harvested_index.json) and per‑component files (data/aceternity/[slug].json, data/shadcn/[slug].json).

How does the server discover available components?

On startup, it fetches

コメント

「その他」の他のコンテンツ