Skip to main content
Glama
esp32-iphone-agent

esp32-iphone-agent

Related Servers

Alternatives to esp32-iphone-agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to see and control a real iPhone over a USB cable on macOS. Provides screenshots, on-screen text reading, taps, swipes, typing, hardware buttons, app launching, and clipboard access without jailbreaking or installing anything on the phone.
      7
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      Control a real iPhone or iOS Simulator through a macOS daemon and XCTest runner over USB or Wi-Fi: read screen text, tap, type, swipe, inspect logs and replay flows with explicit outcomes. Browser sandbox: use readonly to inspect 12 preloaded flows without a phone. Reuse an existing sandbox from MCP Deployments, or delete it before starting another. Device control needs your Mac and iPhone.
      6
      43
      487
      -
    • A
      license
      A
      quality
      B
      maintenance
      Let AI agents operate a real USB-connected iPhone from Linux — no Mac, no jailbreak, no paid developer account. Screenshots, taps, swipes, text input, element tree and app control via WebDriverAgent, with CoreDevice HID fallback.
      17
      40
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a real iPhone from a Mac by reading the screen over USB and sending taps, swipes, typing, and app launches over Bluetooth, with every action returning a fresh screenshot so the agent can verify its work. Runs as a local MCP server, so agents can test iOS apps on physical devices and automate everyday phone tasks.
      38 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server gives AI agents eyes and hands on a real iPhone: they read the screen as a list of elements plus a screenshot, then tap, type, scroll, swipe, answer system permission prompts, press buttons, rotate, and open deep links to test any installed app. It runs over USB or Wi-Fi from Windows, Linux or macOS, with no Mac or Xcode needed, and can be limited to a named set of apps.
      4
      MIT

    TDQS

    B3.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly distinct: screenshot, tap, longpress, swipe, type_text, and the intent_* trio each target a unique action. The main risk is press_key vs press_button, which read similarly as 'press X', though the descriptions explicitly separate keyboard keys from the hardware HOME button. history vs intent_show is also close but differentiated by live-run vs saved-intent scope.

    Naming Consistency3/5

    Conventions are mixed: some tools are bare verbs (tap, swipe), some are verb_noun snake_case (type_text, press_key, press_button), some are bare nouns (screenshot, history, device_info), and the intent group uses noun-first (intent_list, intent_show, intent_save) — the opposite order from press_*/type_*. Still readable, but the inconsistent verb/noun ordering prevents a strong pattern score.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range and each one earns its place: input primitives, observation (screenshot, phone_audio, device_info), audit (history), and intent persistence. No redundant or filler tools are present.

    Completeness4/5

    The surface covers the full act-observe loop: screenshot, gestures, text/keyed input, device status, audio feedback, history, and intent save/replay. Minor gaps exist — no intent_delete (only overwrite-by-name), no direct app-launch/dismiss affordance beyond the HOME button, and clipboard/paste is absent — but agents can work around these via UI automation.

    Maintenance

    ActivityMaintained
    ResponsivenessUsually handled