AceternityUI_MCP_Server
Related Servers
Alternatives to AceternityUI_MCP_Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI assistants with access to HeroUI component library documentation, enabling them to list components, retrieve detailed API references, and explore customization options for building React applications.2-
- FlicenseAqualityDmaintenanceProvides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.4224-
- AlicenseAqualityBmaintenanceProvides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.5665MIT
- AlicenseAqualityDmaintenanceHelps AI assistants access shadcn/ui component documentation and examples through a TypeScript-based MCP server that provides reference information for component details, usage examples, and search capabilities.41,09560MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to RubyUI component library documentation, including listing components, fetching docs, searching, and getting installation/theming guides.GPL 3.0
- FlicenseNot gradedqualityCmaintenanceProvides AI assistants with comprehensive access to Material UI documentation, component details, and setup guides for building React applications. It enables searching through 50+ components and provides structured information on imports, customization, and best practices.2-
TDQS
Scored across 3 tools
The three tools have distinct purposes: list for browsing, search for querying, and get for retrieving a specific item. However, list with category filtering and search by text could occasionally overlap if users search by category name, but descriptions clarify the intended use.
All tool names follow the consistent verb_noun pattern: get_component, list_components, search_components. The pattern is uniform and predictable.
Three tools is minimal but appropriate for a read-only component browsing server. It covers the core operations without bloat, though one additional tool (e.g., get_categories) might round it out slightly.
For its purpose of browsing a UI component library, the set provides list, search, and detail retrieval—covering the essential workflows. A minor gap is the lack of an explicit category listing endpoint, but list_components with category filtering mitigates this.