Android MCP Toolkit MCP Server

MCP server with useful Android development tools: SVG conversion, Logcat management, and Device automation (dump UI, screenshot, input). The android mcp toolkit mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Small MCP server with three tools: - Fast SVG → Android VectorDrawable conversion (cached, file or inline). - adb logcat reader with package/pid/tag filters for quick crash triage. - Translation length difference estimator to flag risky length deltas before layout breaks.

Adding it to your client

android-mcp-toolkit on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• convert-svg-to-android-drawable — Inputs: svg (inline) or svgPath (file path). Optional: outputPath, floatPrecision (default 2), fillBlack (default false), xmlTag (default false)
• Output — VectorDrawable XML text; also writes to disk when outputPath is provided
• Performance — LRU cache (32 entries) keyed by SVG + options plus fast reuse in-session
• Converter — vendored fork in vendor/svg2vectordrawable with fixes for rgb()/rgba(), hsl()/hsla(), and named colors. Upstream license
• manage-logcat — Inputs:
• action — read (default), crash, anr, or clear
• packageName — Optional. Resolves PID via adb shell pidof
• pid — Optional. Explicit PID
• tag — Optional. Filter by tag (e.g. MyApp)
• priority — V, D, I, W, E, F, S (default V)
• maxLines — Tail count (default 200, max 2000)
• timeoutMs — Default 5000

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Android MCP Toolkit.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the android mcp toolkit mcp server does with a few real requests.

When to reach for it

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Android MCP Toolkit's toolset — convert-svg-to-android-drawable, Output, Performance and 11 more — is a fair guide to whether it matches your workflow. It is maintained by nam0101; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.