convert-svg-to-android-drawable
Convert SVG markup or files into Android VectorDrawable XML quickly, optionally writing to disk.
LABSCO SUMMARY
Two jobs that normally sit outside the device toolchain arrive alongside the device tools.
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.
What it is
An Android toolkit that puts two build-side jobs — asset conversion and localisation length — next to device inspection over logcat, dumpsys and uiautomator.
What you get
- 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
Requirements
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.
Setup effort
One command — npx -y android-mcp-toolkit
USE CASES
01
Turning a designer's SVG into a drawable the build will accept
Hand over the SVG markup or a file path and take back VectorDrawable XML, tinted or forced to black fill, written where the resources live.
02
Catching a translation that will break the layout
Compare the translated string against the source before it ships, with the tolerance set to whatever your tightest screen can actually absorb.
03
Working out what the app was doing when it froze
Pull the ANR check and the crash lines out of logcat, confirm which window actually had focus, and keep the screen as a file for the ticket.
04
Driving the screen from the element you just found in the hierarchy
Dump the hierarchy as XML, pick out the element you want, and send the tap, the text or the key event to it by ID rather than by coordinates.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
dump-ui-hierarchy
Capture the current UI hierarchy as XML using uiautomator.
estimate-text-length-difference
Compare original and translated text lengths to detect layout risk; configurable tolerancePercent (default 30%).
get-current-activity
Inspect current focused app/window via dumpsys window.
inject-input
Simulate user input interactions (tap, text, swipe, keyevents) or click by UI element.
manage-logcat
Unified tool to read logs, capture crashes, check ANRs, and clear buffers.
take-screenshot
Capture device screenshot and save to a local file.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"android-mcp-toolkit": {
"command": "npx",
"args": [
"-y",
"android-mcp-toolkit"
]
}
}
}npx
TERMINAL
npx -y android-mcp-toolkit
