This MCP server wraps the JADX decompiler to provide APK analysis and reverse engineering capabilities through the MCP interface. It exposes a set of core analysis, method, component, resource, and bytecode tools that let you load an APK, inspect classes and methods, decompile source, analyze the AndroidManifest, extract components, and view resource files and bytecode representations. You can integrate these tools with AI assistants or scripting workflows to perform security assessments, code reviews, or targeted analyses of Android applications. To use it, run the server and configure your MCP client (for example Claude Desktop) to connect to the provided Java-based MCP endpoint; then invoke the available tools like load_apk, get_all_classes, get_class_source, and get_exported_components to perform step-by-step APK analysis.

Prerequisites:

• Java 11 or higher
• Maven 3.6+ (for building the fat JAR)

1. Clone the repository git clone <repository-url> cd jadx-mcp-server

2. Build the project (fat JAR with dependencies) chmod +x build.sh ./build.sh

   or build manually with Maven

   mvn clean package

   The resulting JAR should be at:

   target/jadx-mcp-server-1.0.0-jar-with-dependencies.jar

3. Configure Claude Desktop (or your MCP client) Use the sample configuration to point to the built JAR: { "mcpServers": { "jadx-analyzer": { "command": "java", "args": [ "-Dspring.ai.mcp.server.stdio=true", "-jar", "/path/to/jadx-mcp-server/target/jadx-mcp-server-1.0.0.jar" ] } } }

4. Run the server (example) java -Dspring.ai.mcp.server.stdio=true -jar target/jadx-mcp-server-1.0.0.jar

Tips and notes:

• This server is a pure Java implementation (no external plugins). It runs as a standalone JAR on Java 11+.
• The provided Claude Desktop config demonstrates how to connect to the MCP endpoint; adjust the path to the built JAR accordingly.
• Tools cover APK loading, class/method inspection, decompiled source retrieval, manifest analysis, component extraction, and resource/bytecode access.
• Ensure you have the target APK accessible for analysis, and be mindful of large APK sizes which may impact response times.
• If you customize the server, you can enable or disable specific MCP transports and logging via standard Spring Boot and JVM options.