Skip to main content
Glama
ikatkov

iphone-safari-mcp

by ikatkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to iphone-safari-mcp

No user-submitted related servers found.

    Related Servers

    • apex-browser-mcp

      apexradius
      A
      license
      B
      quality
      C
      maintenance
      Local, multi-session MCP server driving real Chrome, Chromium, WebKit, and Safari engines, with attach-to-running-Chrome support, no API keys or cloud required.
      10
      MIT

    • OpenSafari

      shaun0927
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for headless mobile QA automation that controls real Safari, Flutter, and native iOS apps on Xcode Simulators via WebKit Remote Debugging Protocol, enabling parallel multi-device testing and persistent login sessions.
      44 npm
      15
      MIT

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      4 npm
      2
      MIT

    • lazy-mobile-mcp

      leaf76
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for Android and iOS mobile automation and performance telemetry, enabling device control (screenshot, tap, swipe, input, app launch) and metric collection (CPU, memory, launch time) via ADB, simctl, and WebDriverAgent with SQLite session history.
      9 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.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: navigate vs. reload_page vs. go_back are separate navigation actions; click vs. tap distinguish element-based from coordinate-based interaction; screenshot, snapshot, and page_source each offer a different view of the page. There is no meaningful overlap that would cause an agent to misselect.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern (navigate, reload_page, evaluate_javascript, install_console_capture), with a few single-verb commands (click, tap, scroll) and noun-like names (screenshot, snapshot, page_source) that act as commands. All names are lowercase snake_case, which keeps the set predictable and readable despite minor pattern deviations.

    Tool Count4/5

    With 16 tools, this server sits just above the ideal 3-15 range, but each tool covers a distinct aspect of mobile browser automation—navigation, interaction, inspection, and session control. The count is justified by the breadth of features needed for iPhone Safari and does not feel bloated or redundant.

    Completeness4/5

    The tool set covers the core lifecycle of a browsing session: navigate, go_back, reload, click/tap/scroll/type, extract page data (snapshot, page_source, screenshot), execute JS, and capture console/network diagnostics. Minor gaps exist (e.g., no explicit wait-for-element or cookie management), but they are workable and the server is functionally complete for typical automation tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources