Component Harvester MCP Server ✨

Created By
dazeba year ago
A Model Context Protocol (MCP) server that automatically discovers, fetches and processes react components from popular react libraries like Aceternity and Shadcn
Overview

What is Component Harvester MCP Server?

The Component Harvester MCP Server is a Model Context Protocol (MCP) server designed to automatically discover, fetch, and process React components from popular libraries like Aceternity and Shadcn.

How to use Component Harvester MCP Server?

To use the server, you can send requests to fetch specific components or lists of components from the supported libraries, and it will return the relevant data, including code and integration instructions.

Key features of Component Harvester MCP Server?

  • Automatic discovery of React components from Aceternity and Shadcn UI libraries.
  • Fetching of full component code and metadata.
  • Generation of detailed integration prompts for easy usage.

Use cases of Component Harvester MCP Server?

  1. Quickly sourcing UI components for React applications.
  2. Automating the integration of components into projects.
  3. Providing detailed instructions for using components from popular libraries.

FAQ from Component Harvester MCP Server?

  • What libraries does it support?

Currently, it supports Aceternity UI and Shadcn UI, with plans to add more in the future.

  • How do I fetch a component?

You can use the scan_aceternity_component or scan_shadcn_component tools to fetch specific components.

  • Is there a way to list all available components?

Yes! You can use the list_harvested_components tool to see all components stored in the index.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dazeb
Star
0
Language
HTML
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago