Skip to main content
Glama
manymids

ARCL CYD Desktop MCP bridge

by manymids
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to ARCL CYD Desktop MCP bridge

No user-submitted related servers found.

    Related Servers

    • uitree-local

      CT-mao
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local, cloud-free control of a Uitree Portal APK via 27 MCP tools for UI tree inspection, screenshots, tapping/swiping, input, clipboard, app/file management, APK installation, and keep-awake.
      -

    • mcp-esp32

      0mandrock1
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with ESP32/MicroPython boards via tools for flashing firmware, running REPL code, file management, and serial capture, with support for progress notifications, cancellation, and error handling.
      8
      MIT

    • adb_mcp_server

      wolfcoming
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote control of Android devices via ADB, including screen operations, input, app management, file transfer, and advanced tools like UI testing and performance analysis.
      24
      MIT

    • flipper-mcp

      yairhdz24
      A
      license
      B
      quality
      B
      maintenance
      MCP server that enables full control of a Flipper Zero device over USB, including screenshots, radio protocols, and app development without requiring a COM port.
      35
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools map to a distinct subsystem and action, and descriptions clearly separate closely related groups like app listing versus installed MicroPython apps. The main ambiguity is an explicit alias (cyd_launch/cyd_activate) and a few read-versus-clear or launch-versus-script variants, but descriptions mostly prevent misselection.

    Naming Consistency4/5

    Names largely follow a consistent cyd_<subsystem>_<action> pattern with snake_case throughout. Minor deviations such as noun-only names (cyd_logs, cyd_diagnostics) and the common arcl_status tool keep it from being perfectly uniform.

    Tool Count2/5

    42 tools is well above the comfortable MCP tool count and will be heavy for an agent to navigate. Many fine-grained operations could be consolidated into parameterized tools, and the launch/activate alias inflates the count further.

    Completeness4/5

    The surface covers core device control well: UI observation, input synthesis, app lifecycle, settings, Bluetooth, radio, and shortcuts. Minor gaps like an explicit app-stop or standalone reboot tool and generic SD file browsing prevent a perfect score.

    Resources