Skip to main content
Glama
Sign In
MCP 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

    • mobile-mcp

      saurabhnew119-bot
      A
      license
      B
      quality
      B
      maintenance
      Enables agents and LLMs to automate and develop native iOS and Android apps across simulators, emulators, and real devices through a single platform-agnostic, accessibility-first interface. Provides taps, swipes, text input, app install/launch, screenshots, screen recording, device logs, and crash reports without requiring any iOS- or Android-specific expertise.
      35
      57,882 npm
      Apache 2.0

    • 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
      B
      quality
      A
      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.
      18
      3
      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 have clearly distinct purposes, and the descriptions actively resolve the riskiest overlaps (appium_gesture vs appium_perform_actions, appium_find_element vs appium_find_elements, generate_locators vs appium_generate_tests, appium_find_element vs appium_gesture scroll_to_element). Remaining soft spots are appium_get_text vs appium_get_element_attribute (value/property) and the grab-bag appium_app_lifecycle that bundles install, state, deep links, and data clearing behind one name.

    Naming Consistency3/5

    The bulk of tools use a predictable appium_<noun>_<verb> snake_case convention, but several break the pattern: prepare_ios_simulator, select_device, and generate_locators lack the appium_ prefix, and prepare_ios_simulator vs appium_prepare_ios_real_device use inconsistent phrasing for parallel operations. The naming is readable but not a single uniform scheme.

    Tool Count2/5

    At 32 tools this is well past a well-scoped set, and several small single-purpose getters (appium_orientation, appium_get_window_size, appium_mobile_device_info, appium_get_active_element) could be folded into broader grouped tools. Mobile automation is a broad domain, but the surface still reads as accumulated rather than curated.

    Completeness4/5

    Coverage is strong across the full mobile automation lifecycle: device prep (simulator and real iOS WDA signing), session management, element location, gestures, text entry, alerts, contexts, files, clipboard, permissions, geolocation, recording, and app lifecycle. Minor gaps and one dangling reference: appium_find_element points to an 'appium_ai' vision tool that is not exposed, and there is no log capture or network-condition tooling.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources