Skip to main content
Glama

Related Servers

Alternatives to Swipium

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      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.
      18
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI agent to boot and control an Android emulator — tapping, typing, scrolling, inspecting screens, reading logs and installing APKs — and to record those interactions as replayable, CI-ready test flows. Actions are captured by element text or id rather than coordinates, so the saved tests survive layout changes and rerun without the agent.
      18
      1
      MIT
    • 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
      45,799 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to interact with iOS Simulators and Android Emulators, allowing autonomous app development, UI interaction, profiling, and debugging through natural language.
      77
      3,195
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 55 tools

    Disambiguation3/5

    Many tools overlap in the high-level orchestration space: qa_test_this, qa_test_feature, qa_mobile_audit, qa_smoke, qa_explore, and qa_prepare_target all 'prepare/run tests on a device.' Descriptions add clarifying notes (e.g. qa_test_this 'start here', qa_start_session for low-level), but an agent must read carefully to choose. Lower-level tools (qa_act, qa_snapshot, qa_inspect, qa_visual) are distinct.

    Naming Consistency4/5

    Consistent qa_ prefix and snake_case throughout. Most are verb_noun (qa_start_session, qa_get_artifact, qa_clean_overlay) but several are noun-first (qa_app_map_read, qa_suite_read, qa_job_status, qa_device_info, qa_screen_record), a minor deviation.

    Tool Count2/5

    55 tools is heavy for a mobile QA server; groups like app-map (5), suite (5), flow (4), and the many orchestrators suggest feature sprawl. Each earns some purpose but the surface is bloated and would benefit from consolidation.

    Completeness5/5

    Covers the full lifecycle: device/emulator management, WDA, build/bundletool, prepare, session, snapshot/act, flows, suites, app maps, visual checks, health, reports, job control, blocker recovery. No obvious dead ends in the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues