Skip to main content
Glama
Famel-svg

apk-preview-mcp

by Famel-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to apk-preview-mcp

No user-submitted related servers found.

    Related Servers

    • DroidLab MCP

      cirkasssian
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to fully control an Android emulator via MCP, including UI interaction, screenshots, APK installation, logging, and clipboard access, with optional live browser viewing for humans.
      MIT

    • mobila

      mamayevets
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to control an Android emulator via MCP, allowing tasks like tapping, typing, swiping, taking screenshots, and installing apps through natural language commands.
      MIT

    • Phone for AI MCP

      lllq-123
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to operate a spare Android phone through MCP: capture screenshots, inspect UI controls, tap/swipe, input Chinese text, launch apps, and optionally run rooted shell commands or transfer files. It also supports a live web console for remote viewing and control.
      18
      MIT

    • Codex Android MCP

      zifanersuotang
      A
      license
      A
      quality
      C
      maintenance
      Enables Codex to inspect, test, and control Android emulators through adb with strict typed tools, returning screenshots as native MCP images and keeping physical devices and Gradle execution behind explicit opt-in policies.
      19
      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.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct stage or action in the APK preview workflow: diagnosis, AVD listing, session lifecycle, installation, app listing, launching, display configuration, screen inspection, interaction, and session teardown. There is no meaningful overlap or ambiguity between tool purposes.

    Naming Consistency5/5

    All tools follow the same `apk_preview_` prefix with a clear verb_noun pattern (e.g., start_session, install_apk, stop_session). This is highly predictable and consistent across the entire set.

    Tool Count5/5

    Ten tools provide a focused but complete toolset for the APK preview use case without unnecessary bloat. Each tool earns its place in the emulator workflow.

    Completeness4/5

    The toolset covers the full preview lifecycle: setup, session start, install, launch, inspect, interact, configure, and stop. Minor gaps exist such as no explicit uninstall or text input, but these do not block the core preview workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources