ArkUIBuilder MCP
Related Servers
Alternatives to ArkUIBuilder MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables AI assistants to search a catalogue of plain HTML, CSS and JavaScript UI components and fetch each one's exact files, settings and framework integration instructions. Lets users add production-ready interface components by asking in natural language.22-
- AlicenseAqualityCmaintenanceProvides documentation search, reading, and AI-powered Q\&A for ArkTS/ArkUI development, enabling AI coding assistants to answer questions and retrieve official docs.743MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.-

QuasarUI MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to search a catalogue of Quasar Framework components and paste their source code directly into a project, exposing free components to anyone and paid components when an access key is supplied.5304 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables coding agents to search, inspect, and retrieve real UI components from existing component libraries, with ranked results, score explanations, licence and provenance details, and safe installation plans. It also surfaces similar components and higher-level UI patterns so agents can reuse existing interface code instead of generating it from scratch.44 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to retrieve React, Svelte, Vue, and React Native component source code, demos, blocks, and metadata for building UIs in AI-powered development workflows.108,219 npmMIT
TDQS
Scored across 3 tools
search_widgets (discover), get_widget (inspect source/details), and add_widget (install into module) have distinct actions, and the descriptions explicitly steer between them (e.g. 'to use it as-is call add_widget instead'). There is mild overlap since search results already return the build() call and parameters, making get_widget's unique value narrower, but the boundaries are clearly drawn.
All three tools follow a clean verb_noun snake_case pattern: search_widgets, get_widget, add_widget. The convention is predictable and consistent throughout.
Three tools is on the thin side, but the server's scope (search a widget catalog, inspect a widget, install it) is genuinely narrow, so each tool earns its place. A list-categories or remove-widget tool would round it out but the count is reasonable for the purpose.
The core lifecycle of discover -> inspect -> install is fully covered, including an overview mode (search with no args) and a copy/install operation. Minor gaps exist (no tool to remove or update an already-installed widget), but these are workarounds an agent can handle manually.