Skip to main content
Glama
Mobile Next MCP Server

Mobile Next MCP Server

Official
by mobile-next

Related Servers

Alternatives to Mobile Next MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables scalable mobile automation for iOS and Android through a platform-agnostic interface, allowing LLMs to interact with mobile applications via accessibility snapshots or screenshot-based inputs.
      19
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for mobile automation and development, offering a single API to control iOS and Android devices (simulators, emulators, real devices) through accessibility trees and coordinate-based interactions. It lets AI agents launch apps, tap, swipe, type, capture screenshots, and extract structured data from native mobile apps.
      23
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server for ad-hoc UI testing of Android and iOS apps, enabling LLM agents to interact with mobile app UIs and react to observations.
      40
      7 npm
      3
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server for mobile automation that enables LLMs to interact with Android and iOS devices through screenshot, tap, swipe, log analysis, and app lifecycle management.
      32
      20 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to control and automate Android devices through natural language, supporting actions like app management, UI interactions, and device monitoring.
      60
      MIT

    TDQS

    B3.4/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools target a distinct action on a distinct resource, and the local-vs-remote device split is explicitly disambiguated in the descriptions (mobile_list_available_devices vs mobile_list_remote_devices). Minor overlaps remain: mobile_take_screenshot vs mobile_save_screenshot return an image vs write a file, and mobile_press_button is vague about which buttons are accepted. mobile_batch_commands duplicates other tools by design but its description scopes it as a meta-tool.

    Naming Consistency4/5

    Nearly every tool follows a clean mobile_verb_noun pattern (mobile_launch_app, mobile_list_apps, mobile_set_orientation), which makes scanning and grouping easy. The deviations are small but real: get_more_tools has no mobile_ prefix, mobile_batch_commands and mobile_clipboard use a noun rather than a verb, and mobile_press_button omits the target object unlike its siblings.

    Tool Count3/5

    36 tools is heavy and sits above the comfortable range, though the domain is genuinely broad (device discovery, remote cloud allocation, app lifecycle, gestures, capture, logs, crashes, location, clipboard). Some entries could be consolidated, notably take_screenshot/save_screenshot and the many single-purpose setters. It is defensible but toward the bloated end for the stated purpose.

    Completeness4/5

    Coverage of the mobile automation lifecycle is strong: device listing/allocation/release, app install-launch-clear-uninstall, full gesture and input set, screenshots and recording, logs, crash reports, orientation, location and clipboard. The main gaps are file push/pull and permission or network-condition manipulation, which agents can sometimes work around via batch flows and shell-adjacent tools but not cleanly.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling