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
      49,085 npm
      2
      Apache 2.0

    • mobile-mcp

      Kavya55
      A
      license
      A
      quality
      C
      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
      49,085 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
      13 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
      13 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.
      58
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools target a clearly distinct action+resource (launch vs terminate vs install vs uninstall, click vs double_tap vs long_press, local vs remote device listing). The main ambiguity is the mobile_take_screenshot / mobile_save_screenshot pair, and gesture tools overlap slightly, but descriptions mostly disambiguate them.

    Naming Consistency5/5

    Every tool uses the mobile_ prefix with consistent snake_case verb_noun phrasing (mobile_launch_app, mobile_get_screen_size, mobile_list_elements_on_screen). No camelCase or stylistic deviations anywhere in the set.

    Tool Count2/5

    33 tools is well above the practical ceiling for a single coherent surface, even for rich mobile automation. Several tools are closely related (take/save screenshot, three gesture variants) and could be consolidated, making the set heavier than it needs to be.

    Completeness4/5

    The surface covers an impressive lifecycle: device discovery/allocation/release, app install/launch/terminate/uninstall, input, screenshots, recording, logs, crashes, location, orientation, and clipboard. Only minor gaps remain (e.g. file push/pull, network condition control), which are workable.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources