Skip to main content
Glama
Sign In
@mgcrea/mcp-ios-simulator

@mgcrea/mcp-ios-simulator

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @mgcrea/mcp-ios-simulator

No user-submitted related servers found.

    Related Servers

    • Simulator MCP

      992429169
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to control iOS simulators through the MCP protocol. Supports device management, UI automation, and network interception including screenshot capture, text input, and HTTP request mocking.
      -

    • Shotter

      nathanstitt
      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.
      15 npm
      MIT

    • Testa

      valewnrt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to inspect the iOS Simulator's screen as compact text and perform real touch gestures, typing, assertions, and device controls without requiring testIDs.
      3
      MIT

    • iPhone MCP

      blitzdotdev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control real iPhones and simulators on macOS, allowing for UI interaction, testing, and automation.
      65 npm
      95
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 25 tools

    Disambiguation5/5

    Boundaries are explicitly documented: tap vs tap_element, screenshot vs ui_tree, terminate vs uninstall vs erase, list_crash_logs vs get_crash_log are all distinguished in their descriptions with guidance on when to use each. Pairs like diagnostics/list and wait_for_element/settle_ms are clarified rather than overlapping. No two tools appear to do the same thing.

    Naming Consistency4/5

    Every tool uses the ios_simulator_ prefix and snake_case, which is highly predictable. The verb/noun pattern is slightly mixed (list_apps, tap_element vs ui_tree, diagnostics, screenshot), so it is not a single uniform verb_noun convention, but it remains readable and consistent in style.

    Tool Count4/5

    25 tools sits at the heavy end of the scale, but each maps to a distinct simulator capability (lifecycle, input, UI inspection, logs, media, environment) with no filler. Slightly over the ideal range but well justified for a full simulator automation surface.

    Completeness4/5

    Covers device lifecycle (boot/erase/install/launch/terminate/uninstall), full UI driving (tree/screenshot/tap/swipe/type/button), logs, crash logs, push, deep links and media. Minor gaps remain: no delete-simulator tool despite list mentioning deletion, and gestures like long-press, pinch/zoom and orientation rotation are absent.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources