jadx-mcp-server and adb-mcp
These are complementary tools: JADX-MCP analyzes Android app code statically through decompilation, while ADB-MCP enables dynamic interaction with running Android devices, allowing developers to use both for comprehensive app inspection and testing workflows.
About jadx-mcp-server
zinja-coder/jadx-mcp-server
MCP server for JADX-AI Plugin
Implements a Python-based MCP server that bridges LLMs with JADX via HTTP requests to a plugin, exposing 20+ tools for live Android APK analysis including class/method extraction, manifest parsing, smali bytecode retrieval, and variable renaming. Communicates with the JADX-AI-MCP plugin using a request-handler architecture that queries the decompiled app context directly, enabling real-time vulnerability detection and code-aware LLM recommendations without context switches.
About adb-mcp
srmorete/adb-mcp
An MCP (Model Context Protocol) server for interacting with Android devices through ADB in TypeScript.
Exposes comprehensive Android device control through stdio-based MCP tools including app installation, logcat filtering, file transfer, shell execution, and UI inspection via screenshot/XML hierarchy dumps. Designed as a Claude Desktop integration that bridges AI models with local ADB commands, supporting Android 8.0+ devices and emulators with configurable ADB paths. Provides both high-level operations (APK deployment, permission management) and low-level access (custom shell commands, activity/package manager control).
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work