Skip to main content
Glama
Sign In
NexusAndroid

NexusAndroid

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to NexusAndroid

No user-submitted related servers found.

    Related Servers

    • 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.
      458
      MIT

    • phone-control

      wxh1783921374-xiaofeng
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive a connected Android phone over ADB with 28 tools covering screenshots and UI inspection, taps/swipes/typing, app install and launch, file transfer, wireless pairing, and one-call scripted flows like tap-by-text and wait-for-text.
      MIT

    • scrcpy-mcp

      karim06226
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices over ADB and scrcpy—taking screenshots, tapping, swiping, typing, launching apps, inspecting UI elements, transferring files, streaming video/audio, and running shell commands. It uses scrcpy's control protocol for fast input and near-instant screenshots, with ADB fallback when scrcpy is unavailable.
      374 npm
      MIT

    • scrcpy-mcp

      luciatyurin95
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to see and control Android devices via ADB and scrcpy, supporting screenshots, taps, swipes, typing, app and UI automation, file transfer, shell commands, clipboard, and audio/video streaming.
      374 npm
      MIT

    • 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.
      374 npm
      MIT

    • scrcpy-mcp

      sLima01457
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents vision and control over Android devices via ADB and scrcpy, enabling screen capture, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, audio/video streaming, and clipboard access.
      374 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

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Each tool targets a fairly distinct domain (screen reading, gestures, messages, files, logs, settings, apps, etc.) and the descriptions explicitly cross-reference each other (e.g. draft defers sending to act, act's `then` defers rendering to look). The main overlaps are info (calls/contacts/calendar) versus functions (AppFunctions for calls/contacts/calendar) and settings versus map (both about Settings screens), which could cause misselection in edge cases.

    Naming Consistency4/5

    All 18 names are single lowercase words with no separators or camelCase mixing, so the style is uniformly applied. However the set mixes verbs (look, act, launch, capture) with nouns (settings, messages, files, apps, map), so the semantic convention is looser than a clean verb_noun scheme.

    Tool Count4/5

    18 tools is on the heavy side of the ideal 3-15 range but each one covers a genuinely separate capability area of phone control (looking, acting, messaging, files, capture, logs, diagnostics, settings discovery). Nothing looks redundant enough to merge without losing clarity.

    Completeness4/5

    Coverage of the phone-control lifecycle is broad: observation (look, web, notifications, logs), interaction (act), data access (messages, files, clipboard, info), app management (apps, launch, functions) and diagnostics (checkup, map). The gaps are mostly deliberate safety omissions (no direct send/call/pay without confirm+accord) and minor ones like media/playback control or keyguard handling.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources