Skip to main content
Glama
457,863 tools. Updated 2026-08-14 18:31

"A tool for decompiling Android APK files" matching MCP tools:

  • Install a mobile app on an Android or iOS device using a local APK or IPA file path. Specify device ID and file path to complete installation.
    Apache 2.0
  • Connect to a Drozer console on an Android device for security testing. Session persists across tool calls; disconnect manually to end it.
    Apache 2.0
  • Installs an APK on an Android device, replacing the existing app. Accepts an explicit APK path or uses the latest Gradle build output, with options for module, variant, device, and permission grants.
    MIT
  • Install an APK directly via adb, bypassing Gradle for faster reinstallation after assembly. Specify the APK path or module and variant.
    MIT
  • Scan binary files (APK, EXE, DLL, SO, JAR) to detect open source components, extract license information, and identify security issues with adjustable analysis depth.
    Apache 2.0
  • Summarizes robot project setup: SDK, Git state, OpModes, subsystem docs, Pedro configuration, hardware-name collisions, APK details, reference library, and Android SDK, then suggests next actions.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • MCP server for static security analysis of Android source code

  • Search the AI Tool Directory catalog: tool details, status checks (alive/acquired/deceased + cause and date), alternatives, and side-by-side comparisons. Read-only.

  • Install APK files on Android devices or emulators. Use this to deploy apps, test builds, or update existing applications by providing the local APK path.
    MIT
  • Install an Android application by providing the device ID and the full path to an APK file on the host machine. The tool pushes the APK to the device and completes the installation.
    Business Source 1.1
  • Decompile Android APK files to extract API endpoints from Retrofit and OkHttp3 annotations. Outputs as plain text or Postman collection for security analysis.
    MIT
  • Build an Android APK using Gradle for a specified module and variant. On failure, receive compiler errors with file:line; on success, get the APK path.
    MIT
  • Installs an Android app bundle by deploying base and config split APK files to a device using adb install-multiple, with options to replace or downgrade.
    Apache 2.0
  • Pull all APK splits for an Android package to a local directory for analysis, backup, or transfer.
    Apache 2.0
  • Sign an Android APK file using a keystore; only the APK path is required, with defaults for debug signing or custom credentials for production.
    MIT
  • Retrieve expansion file information for an app's APK, including size and references, by specifying package name, version code, and expansion file type.
    MIT
  • Installs an APK on an Android device or emulator using adb install -r. Specify the APK path and optionally a device serial to deploy builds directly for testing.
    MIT