Skip to main content
Glama
Sign In
mobile-debug-mcp

mobile-debug-mcp

by clivejefferies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mobile-debug-mcp

No user-submitted related servers found.

    Related Servers

    • DroidAgentKit

      iVamsi
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents real Android development tools—Gradle, adb, logcat, lint, crash triage—through a local, permissioned interface. Enables agents to inspect projects, run safe Gradle tasks, capture logs/screenshots, and triage crashes.
      1
      -

    • ThumbAgent

      LiuShiYi1027
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server that enables AI agents to safely control and observe Android mobile devices, supporting device diagnostics, app lifecycle management, async task execution, and performance monitoring through a policy-constrained interface with explicit confirmations.
      1
      Apache 2.0

    • replicant-mcp

      thecombatwombat
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI assistants to build, test, and debug Android applications by interacting directly with the Android development environment. It provides tools for managing emulators, executing Gradle tasks, running ADB commands, and performing UI automation via accessibility trees.
      14
      105 npm
      19
      MIT

    • admcp

      dima-xd
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that enables AI agents to inspect and debug Android apps and devices through typed tools for UI interaction, logcat, Java/Kotlin and native/Flutter debugging, performance traces, heap dumps, artifacts, and evidence-based diagnostics.
      1
      Apache 2.0
    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

    B3.1/5.0

    Scored across 53 tools

    Disambiguation2/5

    Several tools have nearly identical purposes, especially get_app_readiness vs wait_for_app_ready, and wait_for_ui vs wait_for_ui_change vs wait_for_screen_change. find_element, wait_for_ui, and get_ui_tree also blur resolution/observation boundaries, making misselection likely despite long descriptions.

    Naming Consistency5/5

    Tool names consistently use snake_case, mostly with a verb_noun pattern such as tap_element, start_app, get_debugger_stack, and stop_system_trace. Minor verb-only names like tap and swipe remain clear and internally consistent.

    Tool Count1/5

    53 tools is far beyond a reasonable scoped surface and includes many overlapping wait/readiness/observation helpers. This is an extreme count mismatch for an agent toolset, increasing selection cost and coordination failure risk.

    Completeness4/5

    The surface covers app lifecycle, UI interaction, verification, debugger control, tracing, logs, screenshots, network evidence, build, and install. Minor gaps remain around installation cleanup, permission management, and device-level controls, but core workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources