Skip to main content
Glama
1999AZZAR

scrcpy-mcp

by 1999AZZAR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to scrcpy-mcp

No user-submitted related servers found.

    Related Servers

    • scrcpy-mcp

      JuanCF
      A
      license
      A
      quality
      A
      maintenance
      MCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.
      38
      154 npm
      122
      MIT

    • ADB MCP Server

      LLL-404
      F
      license
      A
      quality
      D
      maintenance
      A MCP server that enables AI assistants to control Android devices via ADB, supporting device info, screen control, input simulation, app management, shell execution, file transfer, and UI parsing.
      20
      -

    • androir-mcp

      benasbarciauskas
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that allows AI agents to drive real Android devices via adb, capturing screenshots, reading the live UI tree, and performing actions like tap, swipe, and type.
      13
      5 npm
      1
      Apache 2.0

    • scrcpy-mcp

      wu9853
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server gives AI agents vision and control over Android devices through ADB and scrcpy, enabling screen capture, taps, swipes, typing, app launching, UI element inspection, file transfer, and shell commands. It uses scrcpy's binary control protocol for fast input and near-instant screenshots, falling back to ADB when scrcpy is unavailable, and also supports video and audio streaming plus recording.
      154 npm
      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.5/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (tap vs swipe vs long_press vs drag_drop), and the session-dependent note for several is helpful. Minor overlap exists between ui_find_element, ui_tap_element, ui_get_state, and ui_wait_for_element, which all touch UI exploration, but their actions differ enough to distinguish. These UI tools could occasionally be confused by an agent.

    Naming Consistency4/5

    Naming follows a good snake_case verb_noun pattern throughout (screen_on, app_start, file_push). Minor inconsistencies exist: some tools use device_*, some screen_*, some app_*, and UI tools mix ui_* with standalone form_fill and scroll_to_element. Most follow convention but the ui helper tools break the pattern slightly.

    Tool Count3/5

    46 tools is heavy, near the upper boundary of reasonable. The count is justified for the breadth of the domain (device control, UI automation, file management, video streaming, session management), but several tools overlap functionally (ui_find_element and ui_get_state, or app_list vs file_list) suggesting consolidation could reduce the count. It's not chaotic, but it's more than strictly necessary.

    Completeness5/5

    The surface is remarkably complete for an Android automation server: device control, input gestures, UI interaction, app lifecycle (start/stop/install/uninstall/list), clipboard, files, screen capture/record/video streaming, and a shell_exec escape hatch solves any gaps. No obvious dead-end operations exist, and fallback behaviors are described for tools requiring a session.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources