The device half is deliberately consolidated: manage-logcat covers reading, crash capture, ANR checks and clearing behind one action parameter, and inject-input covers taps, text, swipes and key events either by raw command or by element. estimate-text-length-difference is the unusual one — it sets translated text against the source with a tolerancePercent defaulting to 30%, which catches an overflowing string at the point it is written rather than after someone screenshots the broken screen.
An Android toolkit that puts two build-side jobs — asset conversion and localisation length — next to device inspection over logcat, dumpsys and uiautomator.
- SVG markup or files converted into Android VectorDrawable XML, with tint, black fill, float precision and XML tag options, returned or written straight to disk
- Source and translated strings compared for length against a configurable tolerancePercent that defaults to 30%, so layout risk surfaces before the screenshot does
- Logs read, crashes captured, ANRs checked and buffers cleared through a single logcat tool, filtered by package, pid, tag, priority or line count
- The focused app and window read through dumpsys window, and the UI hierarchy captured as XML through uiautomator
- A device screenshot saved to a local file
- Input simulated on the device — tap, text, swipe, key events — either by command arguments or by clicking a named UI element
A connected Android device or emulator for the logcat, dumpsys, uiautomator, screenshot and input tools; each of those takes a timeoutMs and acts on the attached device. The SVG conversion and the translation length check need neither — they work on markup, file paths and strings. No credentials.
One command — npx -y android-mcp-toolkit