Skip to main content
Glama
teangtang1122

DSH Phone Control

by teangtang1122
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to DSH Phone Control

No user-submitted related servers found.

    Related Servers

    • android-mcp

      ouchi-dev
      A
      license
      B
      quality
      C
      maintenance
      Enables any MCP assistant to see and operate an Android phone or emulator over plain adb, reading the accessibility tree to tap elements by name and also supporting screenshots, typing, swiping, app launching and installation, and logcat — with nothing installed on the device and no root required.
      13
      MIT

    • webadb-agent

      abewartech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control a physical Android device or Docker-hosted emulator over ADB by taking screenshots and performing taps, swipes, key presses, text input, shell commands, app launches, and device info queries. It runs as a local MCP stdio server alongside a web UI and REST API for remote access.
      1
      MIT

    • scrcpy-mcp

      olgajuncker503
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives MCP-compatible AI assistants vision and control over Android devices — capturing screenshots, tapping, swiping, typing, launching apps, inspecting UI elements, streaming audio/video, transferring files, and running shell commands over ADB, with a fast binary control protocol for near-instant input and screenshots.
      151 npm
      MIT

    • android-adb-mcp

      GhostFaceModz
      A
      license
      B
      quality
      B
      maintenance
      MCP server that lets an AI assistant see and control an Android phone over ADB: screenshots, UI dump, tap, swipe, type, keys, open apps. Safety guards: device allowlist, sensitive-app block, raw shell off by default, rate limit.
      14
      72 npm
      1
      MIT

    • scrcpy-mcp

      Monika05274
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI assistants to see and control Android devices through screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming. It connects over ADB with optional low-latency acceleration for faster input and near-instant screenshots.
      151 npm
      MIT

    • scrcpy-mcp

      Tariqn50584
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP-compatible AI assistants to Android devices, letting them see the screen and act on it through screenshots, taps, swipes, typing, app and UI management, shell commands, file transfer, and clipboard access. It routes interaction through scrcpy's control protocol for fast input and near-instant screen captures, falling back to ADB when no session is active, and adds audio/video streaming and recording.
      151 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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The five tools map to distinct stages of phone control: status, app listing, observation, app launching, and actions. phone_action is broad and overlaps slightly with phone_open_app and observation-related interactions, but the descriptions clarify the intended boundaries.

    Naming Consistency4/5

    All names use the phone_ prefix with snake_case, which is highly predictable. However, the suffixes mix nouns (status, apps, action) and verbs (observe, open_app), so it is not a strict verb_noun convention throughout.

    Tool Count5/5

    Five tools are well-scoped for a fixed Android phone control server. Each tool covers a necessary part of the observe-act lifecycle without obvious redundancy.

    Completeness4/5

    The surface covers device status, app discovery, observation, app launching, and core interactions such as tap, swipe, key, and text input. Minor gaps may exist around app lifecycle or waiting behavior, but the core automation workflow is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources