Skip to main content
Glama
hieudtr8

phantom-touch

by hieudtr8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to phantom-touch

No user-submitted related servers found.

    Related Servers

    • IDB-MCP

      askui
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server to control iOS simulators for automation, enabling device management, input control, and screen capture via Facebook IDB.
      11
      MIT

    • app-screen-mcp

      xmuweili
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for reliable iOS Simulator automation that enables agents to control devices, read accessibility UI trees, and capture screenshots. It supports deterministic grounded actions like tapping, typing, and swiping to create a closed-loop observe-reason-act cycle.
      15
      2 npm
      2
      MIT
    • SilbercueSwift by Silbercue

      SilbercueSwiftofficial

      Silbercue
      A
      license
      Not graded
      quality
      B
      maintenance
      High-performance MCP server for iOS development and test automation. Gives AI coding assistants direct access to iOS simulators with sub-20ms screenshots, UI interaction, building, testing, and an intelligent operator mode.
      8
      MIT

    • ios-sim-mcp

      artmamedov
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for iOS Simulator automation. Enables AI assistants to visually interact with iOS apps running in the simulator.
      22 npm
      1
      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.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., pt_launch_app vs pt_list_apps). However, pt_type_text and pt_fill_input both handle text input, and pt_list_elements vs pt_list_inputs have some overlap, though descriptions clarify their specific use cases.

    Naming Consistency5/5

    All tools consistently use the pt_ prefix with verb_noun snake_case naming (e.g., pt_boot_simulator, pt_get_clipboard, pt_list_inputs). The pattern is predictable and uniform across the entire set.

    Tool Count4/5

    18 tools is on the higher end for simulator automation, but each tool covers a distinct operation (simulator control, app management, interaction, input). The count feels slightly heavy yet justified for the comprehensive feature set.

    Completeness4/5

    The server covers core simulator workflows: controlling simulators, launching apps, UI interaction, text input, and screen inspection. Missing features like device orientation or push notification simulation, but these are secondary and do not block primary automation tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources