Skip to main content
Glama
Jiangrong-W

Android REA

by Jiangrong-W
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android REA

No user-submitted related servers found.

    Related Servers

    • scrcpy-mcp

      beatriz4020
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to visually perceive and directly control Android devices via ADB and screen-control tooling, including screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.
      365 npm
      MIT

    • scrcpy-mcp

      Jisungl03
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices through ADB and screen mirroring, supporting screen capture, touch input, app management, UI element finding, file transfer, shell commands, clipboard access, and audio/video streaming.
      365 npm
      MIT

    • scrcpy-mcp

      HelgaLefebvre02469
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices through ADB and scrcpy, supporting screen capture, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.
      365 npm
      MIT

    • scrcpy-mcp

      HuseyinTorres524
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices, with fast input, screenshots, UI element discovery, app and file management, shell access, and audio/video streaming or recording.
      365 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

    C2.9/5.0

    Scored across 89 tools

    Disambiguation2/5

    The 89-tool surface has several overlapping clusters: ADB package inspection vs. Android package inspection vs. APK pulling, screen capture vs. UI capture, static native procedure/address tools vs. analysis tools, and trace/run/storage tools that are related but easy to confuse. Individual descriptions are detailed, but at set level an agent faces many similarly named read/inspect/list operations with subtle boundary differences.

    Naming Consistency2/5

    Names mix several conventions: verb_noun (list_adb_packages, inspect_adb_device), noun_verb-like (procedure_callees, address_name), bare nouns (binary_session, xrefs), and inconsistent prefixes such as read_, inspect_, list_, get_, start_, create_, collect_, snapshot_, map_. The pattern is readable in places but not predictable across the whole set.

    Tool Count1/5

    Eighty-nine tools is far beyond a well-scoped set for an MCP server, even for a complex Android reverse-engineering domain. Many capabilities are split into very granular operations, making discovery and selection burdensome rather than cohesive.

    Completeness4/5

    The surface covers an unusually complete Android RE lifecycle: projects and evidence, APK/resource inspection, ELF/native analysis, ADB device operations, Frida tracing, UI snapshots/actions, storage acquisition/diffing, and workspace export/import. Minor gaps exist around mutating settings or deleting projects, but the major workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources