Rixmerz

Android Layout Inspector MCP — AI skill for Claude Code

AI community

Spatial inspection of a live Android UI for AI agents — finds overlapping views, clipping, touch targets under 48dp, occluded controls and unlabeled clickables by measuring real uiautomator geometry o.

How to install Android Layout Inspector MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Rixmerz/android-layout-inspector-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Android Layout Inspector MCP does

Alternatives in AI

Module Feature — Add a new feature (model + service + controller + views + routes + tests) to an existing module 407 ★
Konnect — AI-assisted PCB design for KiCAD 10. Native KiCAD plugin — a single Rust binary exposing 171 schematic, layout 341 ★
SeekerClaw — Turn your Solana Seeker (or any Android phone) into a 24/7 personal AI agent 316 ★

README

android-layout-inspector-mcp

Spatial inspection of a **live Android UI** for AI agents. Pulls the real view hierarchy off a device or emulator over `adb` + `uiautomator`, and reports layout problems as **measured geometry** — overlap area in px², touch targets in dp, clipped fractions — not as an opinion about a screenshot.

The Android counterpart of [layout-inspector-mcp](https://github.com/Rixmerz/layout-inspector-mcp), which does the same job for web pages via Playwright.

Why

An agent that changes a layout has no way to know whether the result overlaps, clips, or leaves a control too small to tap. Screenshots are the obvious answer and the wrong one: judging a 4px collision by looking at pixels is guesswork, and legitimate overlays get reported as bugs.

This measures instead. Every node's bounds, cross-referenced for intersections, with the overlap area in px² and touch targets converted to dp against the device's real density. Deterministic and reproducible: it tells you *which two nodes* collide, not "something looks off". Use a screenshot afterwards to confirm a finding looks wrong to a human, not to find it.

No Android Studio required.

Requirements

Python 3.11+
`uv` — used by the plugin launch path
adb on PATH, or ADB_PATH, or ANDROID_HOME pointing at an SDK that contains platform-tools/adb
A device with USB debugging on, or a running emulator

Install as a plugin

claude plugin install android-layout-inspector --marketplace Rixmerz/claude-plugins

Install as a plain MCP server

git clone https://github.com/Rixmerz/android-layout-inspector-mcp.git
cd android-layout-inspector-mcp
uv sync
claude mcp add android-layout-inspector -- uv run --project "$PWD" android-layout-inspector-mcp