Skip to main content
Glama
OrionArchitekton

orion-phone-mcp

by OrionArchitekton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to orion-phone-mcp

No user-submitted related servers found.

    Related Servers

    • benchfleet-mcp

      benchfleet
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely use real Android phones by listing devices, reading screens and UI elements, tapping, typing, launching apps, and running workflows only within allowed permissions and approvals, with every step recorded in an audit log.
      -

    • nexus-android

      pironjulien
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to see and drive a real Android phone over plain ADB: screenshots and numbered UI trees, gestures, typing with accents and emoji, SMS/RCS reading and prepared replies, notifications, files, and settings, with no root and no app installed on the phone. Safeguards mask security codes and require explicit confirmation before sending, paying, deleting or confirming anything.
      11
      1
      MIT

    • Karagöz

      yagizdo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.
      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.
      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

    B3.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action: status/lease/release handle the session lifecycle, while shot, ui, tap, type, swipe, key, and open cover distinct interaction modes. No two tools could plausibly be confused, and descriptions explicitly steer agents (e.g. tap points come from ui).

    Naming Consistency4/5

    All names are short, lowercase single tokens with a consistent style, which is easy to scan. It is slightly less predictable because most are verbs (tap, type, swipe, open) while a couple are nouns (status, ui), but there is no casing or convention mixing.

    Tool Count5/5

    Ten tools is well-scoped for phone automation: three lifecycle tools plus seven interaction primitives. Each tool earns its place with no redundant entries.

    Completeness4/5

    The surface covers the full loop needed for device control: acquire/release, observe (shot, ui), and act (tap, type, swipe, key, open). Minor gaps exist such as long-press, pinch/zoom, clipboard, or wait/poll operations, but agents can work around these with existing primitives.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources