Skip to main content
Glama
mgcrea

@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.
      1 npm
      MIT

    • iPhone MCP

      blitzdotdev
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to control real iPhones and simulators on macOS, allowing for UI interaction, testing, and automation.
      39 npm
      89
      MIT

    • Mobile Pilot MCP

      bidouilles
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to control iOS simulators through WebDriverAgent, supporting taps, swipes, typing, screenshots, recording, and app actions with a real-time dashboard for visual feedback.
      36
      Apache 2.0
    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

    A4.3/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: simulator state management, app inspection, UI querying, and input injection are cleanly separated. Potentially confusing pairs like tap vs tap_element and list vs list_apps are explicitly disambiguated by coordinate-based vs element-based and simulator-level vs app-level distinctions.

    Naming Consistency4/5

    All tools share the ios_simulator_ prefix and use lowercase snake_case, with most names following an imperative verb style. A few noun-like names (diagnostics, screenshot, ui_tree, power) deviate slightly from a strict verb_pattern but remain readable and predictable.

    Tool Count4/5

    21 tools is slightly above the ideal 3-15 range, but each tool covers a distinct, justifiable operation across simulator lifecycle, app contrl, UI automation, and state staging. The count feels broad rather than bloated.

    Completeness4/5

    The tool surface covers the main lifecycle: list/boot/install/launch/terminate/erase, plus UI interrogation and interaction, environment staging, media ingestion, and push notifications. Minor gaps like a single-app uninstall or hardware rotation/shake actions exist, but core simulation and UI-testing workflows are well supported.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources