Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

Related Servers

Alternatives to Garmin Simulator MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to build, launch, inspect and drive Garmin Connect IQ apps in the macOS Connect IQ simulator, returning screenshots paired with recognised on-screen text and tap-ready coordinates. It runs whole interaction flows—including the same steps across several watch devices—in a single call, without needing the simulator to be frontmost or the screen unlocked.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to check setup, manage iOS Simulator devices, build/install/launch iOS apps, capture screenshots, send input, and open a live browser preview. It connects local agent workflows to Apple's simulator without requiring a custom emulator or native pane.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automate iOS Simulator interactions including device management, UI element interaction (tap, swipe, type), screenshot capture, and execution of YAML-defined navigation workflows.
      ISC

    TDQS

    B3.2/5.0

    Scored across 46 tools

    Disambiguation3/5

    The broad domains are distinct (lifecycle, input, capture, debug, files), but several boundaries blur: debug_command overlaps state_read/state_seed/state_reset/set_time/phone_message, and reset_state/state_reset/debug_command reset all touch reset behavior. matrix_run vs. build+run vs. dev_loop, and capture_window/get_screenshot/diff_screenshot also require careful reading to choose correctly.

    Naming Consistency4/5

    Names are consistently snake_case and mostly action-oriented, which makes the set readable. The pattern varies between verb_noun (get_screenshot, list_devices), noun_verb (session_start, state_read, simulator_status), and bare utility names (doctor, calibrate), but this is a minor deviation rather than a different convention.

    Tool Count2/5

    At 46 tools, the surface is heavy for a simulator-control server, with many one-off diagnostic, matrix, window, and debug helpers. While the domain is genuinely broad, the count exceeds a well-scoped set and invites tool-selection overhead.

    Completeness4/5

    Coverage is strong across lifecycle, build/run, input simulation, screenshots/diffs, debug-channel state, file snapshots, windows, and diagnostics. Minor gaps remain around explicit baseline management (listing/deleting baselines) and app install/uninstall-style operations, but core workflows are well supported.