Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AndroidMCP Framework

NPM · ANDROIDMCP-FRAMEWORK

MCP server and CLI for Android development and change-aware Android and Flutter testing workflows.

0 this week 71 Trust /100

Last scanned (1 hour ago)

Scores higher than 40% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 34 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to kshivam1177/android-mcp-framwork). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2653 tokens (~88/item across 30 items; 30 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 27 Oct 26 +20
    • CVE-2026-41650 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → 0.86 ▲ functional
  • 26 Oct 26 51

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/androidmcp-framework@0.1.12

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo kshivam1177/android-mcp-framwork
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/kshivam1177/android-mcp-framwork/.github/workflows/publish.yml@refs/heads/master
Rekor log index 3490076700
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9c4fdc63f45e41efffe994d346f282583ba7de7d6181120abed36bc06f0733781019e5708ef587c5312294ae6f83986830aa8eed933ce9dd4ea883e40

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-gh4j-gqv2-49f6 CVE-2026-41650 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 112 packages
Packages resolved 112
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 30 exposed · ~2,653 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
batch ~78

Run several same-screen UI actions in one call, resolving the target once and reusing it for every step. Use for multiple taps/toggles with no intermediate assertion needed - if you need to check state between steps, call the individual tools instead so you can inspect each result.

NameTypeReqDescription
stepsarrayyes–
targetIdstring––

No output schema declared.

No examples provided.

build_device ~152

Compile-only build for a Gradle module + variant (assemble<Variant>). Does not install or launch. Works identically whether you plan to target an emulator or a physical device - both use the same adb, unlike Xcode's simulator/device split.

NameTypeReqDescription
extraArgsarray–Extra raw Gradle CLI args, e.g. ["--stacktrace"].
modulestring–Gradle module path, e.g. ":app". Falls back to sessionDefaults.module.
projectPathstring–Gradle project root. Falls back to sessionDefaults.projectPath.
variantstring–Build variant, e.g. "debug" or "devDebug". Falls back to sessionDefaults.variant.

No output schema declared.

No examples provided.

build_run_device ~161

One-shot: build a module + variant, install it, and launch it. Resolves the target automatically - an explicit targetId wins, then the active session default, then whichever single emulator/device is connected; if more than one is connected without a pin, this fails with the candidate list instead of guessing. Launches via the default launcher activity unless `activity` is given.

NameTypeReqDescription
activitystring–Fully-qualified activity to launch, e.g. "com.example.app.MainActivity". Defaults to the app's launcher activity.
extraArgsarray––
modulestring––
projectPathstring––
targetIdstring–adb serial. Auto-resolved if omitted.
variantstring––

No output schema declared.

No examples provided.

button ~50

Press a named hardware/system button: home, back, recents, power, volume_up, volume_down, menu, enter, camera.

NameTypeReqDescription
buttonstringyes–
targetIdstring––

No output schema declared.

No examples provided.

clear_app_data_device ~56

Reset an app to first-install state on the resolved target (adb shell pm clear) - wipes the app's data and cache without uninstalling it.

NameTypeReqDescription
packageIdstringyes–
targetIdstring––

No output schema declared.

No examples provided.

doctor ~41

Check Android development prerequisites: adb, Java, Gradle, Android SDK, emulator, build-tools and the optional Google Android CLI integration. This framework does not require Python.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

drag ~137

Press-and-drag from one point to another (adb shell input draganddrop) - for reordering list items or drag targets, where a quick swipe would be interpreted as a flick instead of a hold-and-move. Endpoints can be elementRefs from the latest snapshot_ui, or raw coordinates.

NameTypeReqDescription
durationMsnumber–Default 800.
endElementRefstring––
endXnumber––
endYnumber––
startElementRefstring––
startXnumber––
startYnumber––
targetIdstring––

No output schema declared.

No examples provided.

gesture ~83

Named system gesture presets: expand_notifications, expand_quick_settings, collapse_statusbar (all via `cmd statusbar`, no coordinates needed), swipe_up_from_bottom (home/app-switcher gesture-nav swipe), swipe_down_from_top (notification-shade swipe as an alternative to expand_notifications on older API levels).

NameTypeReqDescription
presetstringyes–
targetIdstring––

No output schema declared.

No examples provided.

install_app_device ~118

Install an already-built APK for a module + variant onto the resolved target. Does not rebuild - run build_device first if sources changed. Pass apkPath directly to skip variant lookup entirely.

NameTypeReqDescription
apkPathstring–Explicit path to a .apk, bypassing module/variant lookup.
modulestring––
projectPathstring––
reinstallboolean–Pass -r to adb install to keep existing app data. Default true.
targetIdstring––
variantstring––

No output schema declared.

No examples provided.

key_press ~104

Send one hardware/software key event (adb shell input keyevent). Accepts either a symbolic Android keycode name (KEYCODE_BACK, KEYCODE_ENTER, KEYCODE_DEL, KEYCODE_TAB) or its numeric code. Prefer button for common hardware buttons (home/back/recents/power/volume) - it maps friendly names for you.

NameTypeReqDescription
keyCodestringyese.g. "KEYCODE_ENTER" or "66".
targetIdstring––

No output schema declared.

No examples provided.

launch_app_device ~117

Launch an already-installed app on the resolved target. Provide packageId directly, or module/variant to look it up from the last build's APK. Uses the app's default launcher activity unless `activity` is given.

NameTypeReqDescription
activitystring––
modulestring––
packageIdstring–Application id, e.g. "com.example.app". Resolved from the built APK if omitted.
projectPathstring––
targetIdstring––
variantstring––

No output schema declared.

No examples provided.

list_devices ~61

List every connected Android target - booted emulators and physical devices together, the same way `adb devices -l` does. Each entry reports id (adb serial), type ('emulator'|'physical'), state, and avdName when resolvable.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

long_press ~72

Long-press either a raw (x, y) point or an elementRef from the latest snapshot_ui output.

NameTypeReqDescription
durationMsnumber–Default 600.
elementRefstring––
targetIdstring––
xnumber––
ynumber––

No output schema declared.

No examples provided.

manage_workflows ~84

List every workflow and which of its tools are currently enabled, or enable/disable a workflow for this running server session. Session-only - it does not edit .android-build-mcp/config.yaml, so restart-persistent changes still belong in enabledWorkflows there.

NameTypeReqDescription
actionstring–Default "list".
workflowNamestring–Required for enable/disable.

No output schema declared.

No examples provided.

pull_file_device ~50

Copy a file or directory off the resolved target onto the local filesystem (adb pull).

NameTypeReqDescription
localPathstringyes–
remotePathstringyes–
targetIdstring––

No output schema declared.

No examples provided.

push_file_device ~47

Copy a local file or directory onto the resolved target (adb push).

NameTypeReqDescription
localPathstringyes–
remotePathstringyes–
targetIdstring––

No output schema declared.

No examples provided.

screenshot ~85

Capture the current screen, return it as an image, and save a copy under .androidmcp-framework/artifacts/screenshots/ by default.

NameTypeReqDescription
outputPathstring–Optional explicit screenshot file path. Defaults to the project artifacts folder.
projectPathstring–Project root for the saved screenshot; defaults to the current working directory.
targetIdstring––

No output schema declared.

No examples provided.

session_clear_defaults ~48

Clear runtime overrides for the active profile (or a named one) - falls back to config.yaml's static sessionDefaults on the next read, not to nothing.

NameTypeReqDescription
profilestring––

No output schema declared.

No examples provided.

session_set_defaults ~112

Set one or more session defaults for the active profile at runtime (in-memory + persisted under the state dir for this profile - not written back to config.yaml). Only the fields you pass are changed; everything else stays as-is.

NameTypeReqDescription
applicationIdstring––
avdNamestring––
gradleTaskPrefixstring––
modulestring––
projectPathstring––
targetIdstring––
variantstring––

No output schema declared.

No examples provided.

session_show_defaults ~56

Show the active session-default profile and its resolved values (config.yaml sessionDefaults, overlaid with any runtime overrides from session_set_defaults). Call this before your first build/run/test call in a session - do not assume defaults are configured.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

session_use_defaults_profile ~58

Switch the active session-defaults profile - useful in a monorepo with several Gradle projects, so each can keep its own remembered projectPath/module/variant/targetId without overwriting the others.

NameTypeReqDescription
profilestringyes–

No output schema declared.

No examples provided.

snapshot_ui ~132

Capture a semantic UI hierarchy for the current screen - every element gets a short-lived elementRef (e1, e2, ...) that tap/long_press/type_text can target directly. Saves the captured hierarchy as JSON under .androidmcp-framework/artifacts/ui-snapshots/ by default.

NameTypeReqDescription
interactiveOnlyboolean–Default true: only clickable/focusable/scrollable/checkable elements or ones with text/content-desc. false returns the full raw tree.
projectPathstring–Project root for the saved JSON snapshot; defaults to the current working directory.
targetIdstring––

No output schema declared.

No examples provided.

stop_app_device ~51

Force-stop a running app on the resolved target (adb shell am force-stop).

NameTypeReqDescription
packageIdstringyesApplication id, e.g. "com.example.app".
targetIdstring––

No output schema declared.

No examples provided.

swipe ~121

Swipe either by explicit start/end coordinates, or a screen-relative direction ("up"|"down"|"left"|"right") computed from the current screen size.

NameTypeReqDescription
directionstring––
distancenumber–Screen-relative distance for direction mode, 0-1. Default 0.6.
durationMsnumber–Default 300.
endXnumber––
endYnumber––
startXnumber––
startYnumber––
targetIdstring––

No output schema declared.

No examples provided.

tap ~75

Tap either a raw (x, y) point or an elementRef from the latest snapshot_ui output. Prefer elementRef - it survives minor layout shifts that would break a hard-coded coordinate.

NameTypeReqDescription
elementRefstring––
targetIdstring––
xnumber––
ynumber––

No output schema declared.

No examples provided.

test_device ~117

Run tests for a module + variant. `instrumented` (default) runs connected<Variant>AndroidTest against the resolved target via ANDROID_SERIAL - needs an emulator or device attached. `unit` runs test<Variant>UnitTest on the JVM instead and needs no target at all.

NameTypeReqDescription
extraArgsarray––
kindstring–Defaults to "instrumented".
modulestring––
projectPathstring––
targetIdstring––
variantstring––

No output schema declared.

No examples provided.

touch ~91

Send a raw touch event (adb shell input motionevent) rather than a full tap/swipe gesture. Use for composing custom multi-point sequences - e.g. DOWN, several MOVEs, then UP - that the higher-level tap/swipe/drag tools don't expose.

NameTypeReqDescription
actionstringyes–
targetIdstring––
xnumberyes–
ynumberyes–

No output schema declared.

No examples provided.

type_text ~97

Type text into whatever field currently has focus. If elementRef is given, taps it first to focus it, then types. Only ASCII-range and common Latin text renders reliably through adb input text - non-Latin scripts and emoji generally need an IME-level workaround this tool does not attempt.

NameTypeReqDescription
elementRefstring–Tapped first to focus, if given.
targetIdstring––
textstringyes–

No output schema declared.

No examples provided.

uninstall_app_device ~61

Uninstall an app (and its data) from the resolved target.

NameTypeReqDescription
keepDataboolean–Pass -k to adb uninstall to keep app data/cache. Default false.
packageIdstringyes–
targetIdstring––

No output schema declared.

No examples provided.

wait_for_ui ~138

Poll the UI until a condition holds, then record the latest snapshot (same caching as snapshot_ui - refs from the result are usable directly). With textContains/resourceId: waits for a matching element to appear (or disappear, if gone:true). With neither: waits for the hierarchy to stop changing between polls ("settled").

NameTypeReqDescription
goneboolean–Wait for absence instead of presence. Default false.
pollIntervalMsnumber–Default 500.
resourceIdstring––
targetIdstring––
textContainsstring––
timeoutMsnumber–Default 10000.

No output schema declared.

No examples provided.

Install

How do I install the AndroidMCP Framework MCP server?

AndroidMCP Framework runs locally as an npm package, launched with npx -y androidmcp-framework. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · androidmcp-framework

# add to Claude Code
claude mcp add kshivam1177-androidmcp-framework -- npx -y androidmcp-framework
Common questions

What is the AndroidMCP Framework MCP server?

AndroidMCP Framework is an MCP server listed in the public MCP registry as io.github.kshivam1177/androidmcp-framework. MCP server and CLI for Android development and change-aware Android and Flutter testing workflows. This page covers its npm package (androidmcp-framework).

Is the AndroidMCP Framework MCP server safe to use?

AndroidMCP Framework scores 71 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AndroidMCP Framework MCP server expose?

AndroidMCP Framework exposes 30 tools: list_devices, build_device, build_run_device, install_app_device, launch_app_device, and 25 more. Their descriptions and schemas cost roughly 2,653 tokens of context every time the server is loaded.

Is the AndroidMCP Framework MCP server still maintained?

AndroidMCP Framework is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the AndroidMCP Framework MCP server under?

AndroidMCP Framework declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.