Fetch HeroUI v2 documentation for guides, customization, frameworks, and API references by providing a doc path such as "guide/installation" or "customization/theme".
MIT
741,183 tools. Updated 2026-11-04 01:35
"MCP server for HeroUI (formerly NextUI) component library integration" matching MCP tools:
- Scans directories to identify files containing legacy HeroUI/NextUI components for migration to HeroUI v3 beta.AGPL 3.0
- List every component in the petal_components library to see what's available before composing HEEx markup.MIT
- Retrieve all components from a specified UI library, such as shadcn, radix, headlessui, material, or primevue, for use in project integration.MIT
- Check the current component library setup status for a specified project directory to identify configuration issues.MIT
- Retrieve a list of all HeroUI v2 components and their slugs to use in subsequent documentation and source code queries.MIT
Matching MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that scans React and Vue projects, extracts component metadata (props, slots, events, imports, usage), and exposes it to AI coding agents via structured tools.71MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to private React component library documentation, props, and code examples through type-safe TypeScript integration.-
Matching MCP Connectors
Verified doc corpora for agents: grep-first retrieval, hashed pages, Merkle+RFC-3161 receipts
Integration Agent
- Inspect the React/TypeScript source code of a HeroUI v2 component to understand its hooks and ARIA wiring. Get a valid slug from list_components first.MIT
- Retrieve complete HeroUI v2 documentation for a single component, including install commands, import statements, usage guidance, and the props/API reference table.MIT
- Get the default tailwind-variants style definition for any HeroUI v2 component to see slot, variant, and color CSS classes. Use this to write custom classNames or build a custom theme.MIT
- Retrieve HeroUI v2's default theme tokens, including semantic colors for light and dark modes plus layout tokens like radius, border widths, opacity, font sizes, and box shadows—no configuration needed.MIT
- Retrieves metadata for a published Figma component using its library key, enabling access to component details from Figma libraries.MIT
- Places an instance of a component on a page at given coordinates, duplicating its shape hierarchy with new IDs and maintaining component link. For library components, include the library file ID.MIT
- Browse JLCPCB's full assembly component library through the authenticated Parts API, with paginated results for convenient navigation.MIT
- Retrieve a summary of a web component library including component count, average health score, grade distribution, and last health check timestamp.MIT
- List all CSS parts across components in a web component library. Optionally filter results by component tag name.MIT
- Identify theming gaps in a component library by analyzing token categories, semantic naming, dark mode support, and coverage score. Get a library-wide theming assessment.MIT
- Retrieve published component sets from a Figma team library. Use it to list reusable UI components for design systems or component discovery.MIT
- Swap a schematic component for a different library part while preserving its existing connections and designator. Specify the designator, new library reference, and optional source library.Apache 2.0
- Place a Figma component instance at specific coordinates, using either a local component ID or a published library component key.MIT
- Retrieve the UUID of EasyEDA's built-in system component library so you can reference it in component and library operations.MIT
- Place a schematic component from a library at specified coordinates using device and library UUIDs. Supports online placement with 'lcsc' library.MIT