Skip to main content
Glama
frndchagas

expo-android

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to expo-android

No user-submitted related servers found.

    Related Servers

    • adb-mcp

      myNameArnav
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for controlling Android devices over ADB, using direct commands and semantic accessibility selectors with a Kotlin helper APK.
      61 npm
      MIT

    • android-mcp-server

      jaye773
      F
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that provides comprehensive Android device automation capabilities through ADB, enabling AI agents to interact with Android devices for testing, automation, and device control tasks.
      1
      -

    • android-mcp-harness

      dajarony
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for Android emulator control, exposing tools to get emulator status, inspect UI tree, capture screenshots, and open App settings via Appium and ADB.
      ISC

    • polyscreen-mcp

      Shenepoy
      A
      license
      A
      quality
      A
      maintenance
      An Android-first MCP server for automating real devices, including multi-display handhelds and emulators, with structured tools for device inspection, input, app lifecycle, and diagnostics via ADB.
      33
      16 npm
      Mozilla Public 2.0
    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

    B3.1/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools are clearly distinct, such as screenshot vs. inspect (with UI parsing) and coordinate-based tap vs. element-based tapElement. Minor overlap exists between devices and doctor, both listing devices, but descriptions differentiate their purposes.

    Naming Consistency3/5

    Naming mixes imperative verbs (tap, swipe, inspect) with verb+noun compounds (findElement, openApp) and a few noun-only names (devices, doctor). The pattern is not fully consistent but remains readable and predictable.

    Tool Count4/5

    At 17 tools, the set is slightly above the ideal 3-15 range, but each tool serves a distinct function in device management, UI interaction, and app handling. The count feels justified for a comprehensive Android automation server.

    Completeness4/5

    The toolset covers core device lifecycle, UI inspection/interaction, and Expo Go installation. Minor gaps include lack of arbitrary APK installation or text clearing, but essential workflows are well represented.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources