Skip to main content
Glama
Sign In
android-layout-inspector-mcp

android-layout-inspector-mcp

by Rixmerz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to android-layout-inspector-mcp

No user-submitted related servers found.

    Related Servers

    • apkscope

      Sachitt-AV-08
      A
      license
      A
      quality
      C
      maintenance
      Enables agents that cannot accept image input to read a running Android app's UI as text — dumping the accessibility/semantics tree, auditing tap targets and overlaps, and rendering pixels as glyphs — and to drive it by tapping elements resolved from their labels. Works without a hosted vision API, using adb against a connected device.
      4
      3
      MIT

    • NexusAndroid

      pironjulien
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to see and drive a real Android phone over plain ADB: screenshots and numbered UI trees, gestures, typing with accents and emoji, SMS/RCS reading and prepared replies, notifications, files, and settings, with no root and no app installed on the phone. Safeguards mask security codes and require explicit confirmation before sending, paying, deleting or confirming anything.
      18
      2
      MIT

    • qa-mcp-server

      Gabnagawo
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform exploratory Android QA over adb through ten typed, validated tools — UI dumps, taps, text input, key presses, screenshots, logcat, APK installs, app launches and configured test suites — behind a command allowlist, sandboxed paths, dry-run mode and a JSONL audit log, so agents can test an app without getting a shell.
      10
      MIT

    • android-phone-mcp

      liush2yuxjtu
      A
      license
      A
      quality
      C
      maintenance
      Enables an AI client to control an Android emulator or USB device over ADB by selecting a device, inspecting the UI hierarchy, and performing taps, swipes, text entry, key presses, and app launches. It relies only on Android platform-tools and exposes a compatible tool surface for phone automation.
      12
      386 npm
      MIT

    • run-sequence-android-mcp

      nasiosheva
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to observe and control Android devices and emulators through plain ADB — taking screenshots, reading the UI hierarchy, tapping, swiping, typing, launching apps, reading logcat, and recording the screen. It also executes multi-step action sequences (tap, swipe, key, wait, text, wait-for-element) in a single tool call.
      27
      MIT
    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.2/5.0

    Scored across 6 tools

    Disambiguation2/5

    detect_issues and accessibility_spatial overlap significantly: both detect touch targets under 48dp, covered interactive nodes, and accessibility labeling problems. inspect_layout and element_context also both expose geometry, though one is screen-wide and the other node-specific, creating boundary ambiguity.

    Naming Consistency3/5

    Four tools follow a verb_noun pattern (list_devices, inspect_layout, detect_issues, compare_orientations), but element_context and accessibility_spatial break the pattern with noun-first names. The mixed conventions are still readable and not chaotic.

    Tool Count5/5

    Six tools is well-scoped for an Android layout inspector: device enumeration, layout inspection, issue detection, deep node context, accessibility-specific checks, and orientation comparison. Each tool has a clear role in the workflow, and the count is neither thin nor bloated.

    Completeness4/5

    The tool surface covers the main inspection lifecycle: enumerate devices, dump layout, identify issues, drill into a node, run accessibility checks, and compare orientations. Minor gaps exist, such as no screenshot capture or explicit way to filter issues by type, but agents can accomplish core layout analysis workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources