Skip to main content
Glama
UI-dbugbridge-mcp

UI-dbugbridge-mcp

Related Servers

Alternatives to UI-dbugbridge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      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.
      2
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables controlling a real iPhone or iPad over USB for app development testing, including building and installing apps, launching with console logs, inspecting the accessibility tree, tapping, swiping, typing, taking screenshots, managing app files, and recording audio.
      29
      1
      MIT
    • 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents such as Cursor and Claude Desktop to read a running debugger's captured console logs and network sessions, inspect full request/response payloads, diagnose crashes and failed API calls, and trigger React Native reloads or the developer menu.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables inspecting, debugging, and safely automating a running Typora instance over local STDIO through an opt-in, reversible renderer bridge that exposes status and capability discovery, structured snapshots, DOM and style queries, short-lived element refs, keyboard and click actions, console/network evidence, and instance lifecycle control. Fixture runs execute read-only in isolated profiles and cannot alter Markdown source, while the bridge listens only on localhost with token authentication.
      28
      MIT

    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.