Build, deploy, drive and debug Android apps: Gradle, emulators, adb, logcat, UI automation
Androidbuild MCP server exists for a simple reason — assistants are far more useful when they can act on Androidbuild directly instead of describing what you should do. Build, deploy, drive and debug Android apps: Gradle, emulators, adb, logcat, UI automation.
Give your AI agent hands on Android. AndroidBuildMCP is an MCP server that lets any MCP client (Claude Code, Cursor, ...) build, deploy, drive and debug real Android apps: Gradle builds with readable errors, emulator management, adb deployment, logcat capture and full UI automation.
Once Androidbuild is connected, these are the calls the assistant has available:
Deploy — build_run compiles, installs and launches in one call. Install/uninstall/clear-data/app-info via adb, with the right device auto-selected when onlyText — heavy screens (e-book WebViews and the like) are capped and searchable with snapshot_ui { filter } instead of flooding the contextdoctor — Check SDK, adb, emulator, avdmanager, Java and connected devices; reports what is missingdiscover_projects — Find Android/Gradle projects under a pathlist_modules — List modules declared in settings.gradle(.kts)list_variants — List build variants of a moduleget_app_id — Read the applicationId of a moduleshow_gradle_config — Show Gradle, AGP, Kotlin and version-catalog entriessession_set_defaults — Set default project, module, variant, serial and appId for all later callssession_show_defaults — Show the current defaultssession_clear_defaults — Clear all defaults, or only the listed keysbuild_app — Build an APK; returns compact file:line compiler errors@asjackson/androidbuild-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Androidbuild's toolset — Deploy, Text, doctor and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dev-jackson; 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.
| Tool | What it does |
|---|---|
| Deploy | build_run compiles, installs and launches in one call. Install/uninstall/clear-data/app-info via adb, with the right device auto-selected when only one is connected. |
| Text | heavy screens (e-book WebViews and the like) are capped and searchable with snapshot_ui { filter } instead of flooding the context. |
| doctor | Check SDK, adb, emulator, avdmanager, Java and connected devices; reports what is missing |
| discover_projects | Find Android/Gradle projects under a path |
| list_modules | List modules declared in settings.gradle(.kts) |
| list_variants | List build variants of a module |
| get_app_id | Read the applicationId of a module |
| show_gradle_config | Show Gradle, AGP, Kotlin and version-catalog entries |
| session_set_defaults | Set default project, module, variant, serial and appId for all later calls |
| session_show_defaults | Show the current defaults |
| session_clear_defaults | Clear all defaults, or only the listed keys |
| build_app | Build an APK; returns compact file:line compiler errors |
| build_run | Build, install and launch in one call |
| test_app | Run JVM unit tests with a parsed pass/fail summary |
**Any other MCP client**
```json
{
"mcpServers": {
"androidbuild": {
"command": "npx",
"args": ["-y", "@asjackson/androidbuild-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.