Skip to main content
Glama
aea91

ArkUIBuilder MCP

by aea91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ArkUIBuilder MCP

No user-submitted related servers found.

    Related Servers

    • UI HUB MCP Server

      jainil224
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.
      -

    • Tessera

      radityama
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      94 npm
      MIT
    • Ruixen MCP Server by ruixenui

      Ruixen MCP Serverofficial

      ruixenui
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to discover, search, and retrieve Ruixen UI components from the live registry, providing installation commands for MCP-compatible clients.
      3
      14 npm
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    All three tools follow a clean verb_noun snake_case pattern: search_widgets, get_widget, add_widget. The convention is predictable and consistent throughout.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources