Skip to main content
Glama
Sign In
Rikinshah787

agent-phone

by Rikinshah787
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to agent-phone

No user-submitted related servers found.

    Related Servers

    • artemis

      AdityaBOL7
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and IDEs to drive real Android devices and emulators for cross-app UI automation, testing, and diagnostics, including collecting Logcat output and screenshots.
      Apache 2.0

    • Android-MCP

      HadyAhmed00
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Android devices and emulators through direct UI interaction, allowing app navigation, automated testing, and real-world task execution via ADB without computer vision or scripts.
      18
      2
      MIT

    • duet

      AdityaSingh-byte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI coding agent to drive a real Android phone over adb and one or more visible Chrome windows in the same test run, with safe guarded commands, screenshots returned as images, per-step logs, reports, and recordings. It lets agents act, inspect the screen and device log, fix code, and rerun a scenario until the feature passes.
      27 npm
      3
      MIT

    • android-mcp

      mii-shell
      A
      license
      B
      quality
      B
      maintenance
      Enables an AI agent to drive an Android app under development on a local emulator or connected device through adb, observing the screen and performing taps, swipes, text entry, key presses, waits, screenshots, logcat and crash inspection. It is restricted to debug builds installed via Run in Android Studio, so agents can exercise only the app being developed.
      23
      13 npm
      MIT

    • Karagöz

      yagizdo
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.
      18
      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

    A3.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly different actions: UI interaction, emulator lifecycle, app management, logs, and test recording are well separated. A few boundaries are softer, such as phone_scroll versus phone_swipe, phone_open versus phone_start, and phone_list versus phone_app list, but the descriptions clarify these cases.

    Naming Consistency4/5

    All tools use a consistent lowercase snake_case phone_ prefix, and the test tools form a clear phone_test_start/save/run family. Minor inconsistency comes from some names being resource-oriented (phone_logs, phone_app, phone_shell, phone_key) while others are action-oriented (phone_tap, phone_look).

    Tool Count4/5

    Eighteen tools is slightly heavy but justified by the broad mobile-automation scope, which spans emulator lifecycle, app management, UI interaction, logs, shell access, and test recording. Each tool appears to earn its place, though the set is near the upper end of what feels comfortably scoped.

    Completeness4/5

    The surface covers the core mobile-agent workflow well: boot/stop devices, install/open/manage apps, inspect and interact with the screen, read logs, run shell commands, and record/replay tests. Minor gaps exist around test artifact management (listing, deleting, or editing saved flows) and some device controls are only reachable through phone_shell.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources