Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Mobile Next MCP Server

No user-submitted related servers found.

    Related Servers

    • Mobile Next MCP

      EmpathySlainLovers
      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
      23,436 npm
      2
      Apache 2.0

    • mobile-mcp

      Kavya55
      A
      license
      A
      quality
      B
      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
      23,436 npm
      Apache 2.0

    • Manos MCP

      ryanperkins
      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
      10 npm
      3
      MIT

    • open-mobile-mcp

      xzaleksey
      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
      207 npm
      3
      MIT

    • MCP Android Agent

      nim444
      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.
      59
      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.5/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools map to a clear resource+action (app lifecycle, screen input, orientation, clipboard, logs, crashes, cloud fleet). The only mild overlap is mobile_take_screenshot vs mobile_save_screenshot and the list_available_devices vs list_remote_devices pair, but the descriptions explicitly contrast these, so an agent can reliably choose.

    Naming Consistency5/5

    Every tool uses a uniform mobile_verb_noun snake_case convention (mobile_get_foreground_app, mobile_list_apps, mobile_allocate_remote_device, etc.). Even the meta-tool mobile_batch_commands fits the pattern, so naming is fully predictable.

    Tool Count3/5

    32 tools is on the heavy side for a single server and pushes into the 'too many' range, with several near-sibling input tools (click, double tap, long press, swipe, press button, type keys). However, the domain is genuinely broad (device mgmt, app lifecycle, input, media, diagnostics, cloud fleet), so most tools earn their place.

    Completeness4/5

    Coverage is strong end-to-end: local/remote device discovery, login and allocation lifecycle, app install/uninstall/launch/terminate, full input and navigation primitives, orientation, location, clipboard, logs, crashes, and screen recording. Only minor gaps remain, such as no explicit scroll/pinch or text-clear helper.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources