Skip to main content
Glama
Immmmmmortal1

UI-dbugbridge-mcp

by Immmmmmortal1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to UI-dbugbridge-mcp

No user-submitted related servers found.

    Related Servers

    • astrolabe

      regulusleow
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect and verify mobile UI hierarchies, nodes, styles, screenshots, and runtime attributes of iOS apps in simulators or on USB devices.
      123 npm
      2
      Apache 2.0

    • React Native DevTools MCP

      V3RON
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges React Native DevTools, enabling AI assistants to debug, profile, and inspect React Native applications through a standardized protocol.
      16 npm
      4
      MIT

    • cross-dev-mcp

      WX-DongXing
      A
      license
      A
      quality
      B
      maintenance
      Enables cross-platform real device debugging for React Native development, supporting Android, iOS, and HarmonyOS with real-time connection status, screenshots, logs, diagnostics, evidence, and Codex context.
      7
      18 npm
      1
      Apache 2.0

    • @mgcrea/mcp-ios-simulator

      mgcrea
      A
      license
      A
      quality
      A
      maintenance
      Enables driving an iOS Simulator from a model: taking screenshots, reading the UI tree, tapping, swiping, typing, managing app lifecycle and device state such as appearance, permissions, location, and notifications, without code signing or a physical device.
      21
      314 npm
      MIT

    • TouchBridge

      MarshallBear1
      A
      license
      Not graded
      quality
      A
      maintenance
      TouchBridge is a local-first MCP server for iOS simulators and physical devices, enabling AI to see, control, test, and redesign iPhone screens through a structured screenshot bridge and tool surface.
      5
      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

    Each tool serves a clear, distinct purpose, such as connection setup, UI inspection, element interaction, log retrieval, or runtime auditing. The two deprecated aliases are explicitly labeled as such, minimizing confusion despite their overlap with get_debug_page and inspect_ui.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., get_debug_page, tap_element, run_flow). Deprecated aliases also adhere to this pattern, so the naming style is uniform throughout.

    Tool Count4/5

    With 16 tools, the count is slightly above the typical 3-15 range, primarily due to two deprecated aliases. Excluding those, the 14 unique tools cover the domain comprehensively, making the count reasonable but marginally padded.

    Completeness5/5

    The tool set covers the full lifecycle of UI debugging: connection verification, port forwarding, UI tree inspection, runtime node retrieval, element interaction (tap, switches, text), log searching/waiting, screenshots, and Figma-based auditing. No significant gaps are evident for the stated purpose.

    Resources