Skip to main content
Glama
appium

MCP Appium

Official
by appium
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Appium

No user-submitted related servers found.

    Related Servers

    • @qirabot/mcp

      qirabot
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.
      6
      5 npm
      MIT

    • MCP Appium

      supremehyo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate Android mobile device testing through Appium, with automatic device detection, screen element inspection, and natural language test scenario execution.
      3
      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
    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.7/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action and the descriptions actively cross-reference each other (e.g., appium_gesture defers to appium_drag_and_drop and appium_perform_actions; appium_find_element vs generate_locators vs appium_get_active_element carry priority guidance). Even potentially overlapping gesture and element-lookup tools are clearly separated, so an agent is unlikely to mis-select.

    Naming Consistency4/5

    The dominant appium_ + snake_case pattern is consistent across ~27 tools, but select_device, generate_locators, and prepare_ios_simulator break the prefix convention. Notably, generate_locators vs appium_generate_tests and prepare_ios_simulator vs appium_prepare_ios_real_device are internally inconsistent pairs in the same subdomains.

    Tool Count2/5

    With 31 tools, the surface exceeds the 25+ 'too many' threshold. While Appium's domain is broad, the set is dense and several tools could be consolidated (e.g., the three separate gesture tools, or device_info/orientation/control split across tools), making it heavier than needed for agent usability.

    Completeness4/5

    The surface covers the mobile automation lifecycle well: device selection, session management, element finding/interaction, gestures, app lifecycle, contexts, and device services (permissions, geolocation, clipboard, files, recording). Minor gaps exist — no element clear-text operation, no element location/size retrieval, and no explicit wait-for-element helper — but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources