Skip to main content
Glama
livetaub

PreviewAPK

by livetaub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PreviewAPK

No user-submitted related servers found.

    Related Servers

    • Phone Harness MCP by phone-harness

      Phone Harness MCPofficial

      phone-harness
      A
      license
      A
      quality
      B
      maintenance
      Lets AI agents drive real iPhones and Androids hosted in the cloud over HTTPS — taking screenshots, inspecting on-screen elements, tapping, typing, swiping, and launching apps — with no pairing, adb, or Mac required. It can run locally over stdio or as a hosted streamable HTTP endpoint supporting API keys and OAuth sign-in.
      15
      MIT

    • Droidline

      KnifeLemon
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents see and use a real Android phone over Wi-Fi: read the screen, find elements by text or ID, tap, type, swipe, take screenshots and read notifications, without ADB or root.
      312
      MIT

    • Android MCP

      CursorTouch
      A
      license
      C
      quality
      B
      maintenance
      A lightweight bridge enabling AI agents to perform real-world tasks on Android devices such as app navigation, UI interaction, and automated QA testing without requiring computer-vision pipelines or preprogrammed scripts.
      14
      903
      MIT

    • 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
    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 27 tools

    Disambiguation4/5

    Most tools target distinct actions/resources, and descriptions actively steer agents between similar tools (hierarchy vs observe vs screenshot, tap vs tap_text vs act). A few boundaries still blur: status vs get_links both expose session/driver state, and finish vs stop vs feedback all relate to ending or wrapping up work.

    Naming Consistency4/5

    The previewapk_ snake_case prefix is used consistently across all tools, with most names following a verb_noun or clear resource pattern. Minor deviations exist where noun-only names (hierarchy, device, status) sit alongside action names, but the convention remains readable.

    Tool Count3/5

    27 tools is heavy for a single MCP server and sits in the borderline-overloaded range. Many tools are justified by the broad mobile QA domain, but some consolidation is possible—particularly around recording, observation, and session lifecycle tools.

    Completeness4/5

    The surface covers the full mobile QA lifecycle: device selection, session start/stop, UI observation, gestures, text input, app relaunch, logs, recording, file transfer, device settings, and APK hot-swap. Minor gaps exist, such as standalone long-press/double-tap (only via act) and app-data/network-condition controls, but workarounds are available.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources