Skip to main content
Glama
zunairvf-sys

mobile-freecode

by zunairvf-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to mobile-freecode

No user-submitted related servers found.

    Related Servers

    • phone-control

      sheear
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.
      2 npm
      MIT

    • adb-mcp-server

      sfaizi24
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to control an Android device over the network via ADB, providing tools for shell commands, screen capture, UI inspection, file operations, and input simulation.
      22 npm
      MIT

    • scrcpy-agent

      EF-Code
      A
      license
      B
      quality
      B
      maintenance
      Local MCP server for observing and controlling an authorized Android device over USB using ADB and scrcpy, providing screen capture, UI automation, app inspection, logcat, and evidence recording.
      29
      34 npm
      2
      MIT

    • adb-mcp

      myNameArnav
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for controlling Android devices over ADB, using direct commands and semantic accessibility selectors with a Kotlin helper APK.
      67 npm
      MIT

    • phone-mcp

      PeterTianbuhan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables desktop agents such as Claude Code and Codex to control an Android phone as a long-lived action endpoint, pairing over outbound WebSocket and exposing phone capabilities as MCP tools with local pause and revocation.
      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

    A3.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool maps to a distinct lifecycle stage: discovery (list/get), pairing (pair/unpair), command execution (call), multi-device execution (batch), and screen capture (screenshot/screen_stream). Some overlap exists between 'screenshot' and 'screen_stream'—and 'call' can also trigger screen.screenshot—but the descriptions clarify single-frame versus streaming.

    Naming Consistency3/5

    Names are readable and snake_case, but not one consistent pattern: list_devices/get_device use verb_noun, pair/unpair are simple verbs, call/batch are generic verbs, and screenshot/screen_stream are compound nouns. This is mixed but still understandable.

    Tool Count5/5

    Eight tools is well-scoped for an Android device-control server. Each tool has a clear role, with no obvious filler, and the count sits comfortably in the typical 3-15 range.

    Completeness4/5

    The core lifecycle is covered: discovery, pairing, unpairing, device info, command execution, batch execution, and screen capture/streaming. One minor gap is that the 'call' tool defers to an external docs file and the server exposes no schema-listing for the device tools, which could create dead ends if those device tools change.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources