Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
⚡ Fully automated MCP server built to communicate with JADX-AI-MCP Plugin to analyze Android APKs using LLMs like Claude — uncover vulnerabilities, parse manifests, and reverse engineer effortlessly.
Thanks to these wonderful people for their contributions ⭐
MCP server for JADX-AI Plugin
JADX MCP Server is a standalone Python server that interacts with a modified version of jadx-gui (see: jadx-ai-mcp) via MCP (Model Context Protocol). It lets LLMs communicate with the decompiled Android app context live.
JADX-AI-MCP is a plugin for the JADX decompiler that integrates directly with Model Context Protocol (MCP) to provide live reverse engineering support with LLMs like Claude.
Think: "Decompile → Context-Aware Code Review → AI Recommendations" — all in real time.
sequenceDiagram
LLM CLIENT->>JADX MCP SERVER: INVOKE MCP TOOL
JADX MCP SERVER->>JADX AI MCP PLUGIN: INVOKE HTTP REQUEST
JADX AI MCP PLUGIN->>REQUEST HANDLERS: INVOKE HTTP REQUEST HANDLER
REQUEST HANDLERS->>JADX GUI: PERFORM ACTION/GATHER DATA
JADX GUI->>REQUEST HANDLERS: ACTION PERFORMED/DATA GATHERED
REQUEST HANDLERS->>JADX AI MCP PLUGIN: CRAFT HTTP RESPONSE
JADX AI MCP PLUGIN->>JADX MCP SERVER:HTTP RESPONSE
JADX MCP SERVER->>LLM CLIENT: MCP TOOL RESULT
Watch the demos!
It is combination of two tools:
The following MCP tools are available:
Tools that return decompiled source strip Kotlin compiler metadata (@Metadata /
@DebugMetadata, often 25-50% of a Kotlin dump) by default; pass slim=False for a
raw dump. Stripping never changes line numbers, so with_line_numbers=True and
add_comment(line=...) keep working.
fetch_current_class(slim=True) — Get the class name and full source of selected classget_selected_text() — Get currently selected textget_all_classes() — List all classes in the projectget_class_source(slim=True) — Get full source of a given class (with_line_numbers=True to number the lines for add_comment(line=...))get_method_by_name(slim=True) — Fetch a method’s sourcesearch_method_by_name() — Search method across classessearch_classes_by_keyword() — Search for classes whose source code contains a specific keyword (supports pagination)get_methods_of_class() — List methods in a classget_fields_of_class() — List fields in a classget_smali_of_class() — Fetch smali of classget_main_activity_class(slim=True) — Fetch main activity from jadx mentioned in AndroidManifest.xml file.get_main_application_classes_code(slim=True) — Fetch all the main application classes' code based on the package name defined in the AndroidManifest.xml.get_main_application_classes_names() — Fetch all the main application classes' names based on the package name defined in the AndroidManifest.xml.get_android_manifest() — Retrieve and return the AndroidManifest.xml content.get_manifest_component - Retrieve specific manifest component instead of whole manifest fileget_strings() : Fetches the strings.xml fileget_all_resource_file_names() : Retrieve all resource files names that exists in applicationget_resource_file() : Retrieve resource file contentrename_variable() : Renames the variable within a methodadd_comment() : Adds a comment to a class, method, field or a single code line (line=), shown in JADX-GUI and saved with the project (re-commenting the same target updates it, an empty comment removes it)list_comments() : Lists the comments stored in the project, optionally filtered to one classdebug_get_stack_frames() : Get the stack frames from jadx debuggerdebug_get_threads() : Get the insights of threads from jadx debuggerdebug_get_variables() : Get the variables from jadx debuggerxrefs_to_class() : Find all references to a class (returns method-level and class-level references, supports pagination)xrefs_to_method() : Find all references to a method (includes override-related methods, supports pagination)xrefs_to_field() : Find all references to a field (returns methods that access the field, supports pagination)🔍 Basic Code Understanding
"Explain what this class does in one paragraph."
"Summarize the responsibilities of this method."
"Is there any obfuscation in this class?"
"List all Android permissions this class might require."
🛡️ Vulnerability Detection
"Are there any insecure API usages in this method?"
"Check this class for hardcoded secrets or credentials."
"Does this method sanitize user input before using it?"
"What security vulnerabilities might be introduced by this code?"
🛠️ Reverse Engineering Helpers
"Deobfuscate and rename the classes and methods to something readable."
"Can you infer the original purpose of this smali method?"
"What libraries or SDKs does this class appear to be part of?"
📦 Static Analysis
"List all network-related API calls in this class."
"Identify file I/O operations and their potential risks."
"Does this method leak device info or PII?"
🤖 AI Code Modification
"Refactor this method to improve readability."
"Add comments to this code explaining each step."
"Rewrite this Java method in Python for analysis."
📄 Documentation & Metadata
"Generate Javadoc-style comments for all methods."
"What package or app component does this class likely belong to?"
"Can you identify the Android component type (Activity, Service, etc.)?"
🐞 Debugger Assistant
"Fetch stack frames, varirables and threads from debugger and provide summary"
"Based the stack frames from debugger, explain the execution flow of the application"
"Based on the state of variables, is there security threat?"
Demo: Perform Code Review to Find Vulnerabilities locally
There are two separate connections and each has its own host/port:
┌─────────────┐ --host / --port ┌──────────────────┐ --jadx-host / --jadx-port ┌──────────────────┐
│ LLM Client │ ◄──────────────────► │ jadx-mcp-server │ ──────────────────────────► │ JADX-GUI Plugin │
│ (Claude, │ Where the MCP server │ │ Where the MCP server looks │ (jadx-ai-mcp) │
│ Codex..) │ LISTENS for clients │ │ for the JADX plugin │ │
└─────────────┘ └──────────────────┘ └──────────────────┘
Scenario 1 — Everything on the same machine (most common):
# Default: MCP server on localhost:8651, connects to JADX plugin on localhost:8650
uv run jadx_mcp_server.py --http
Scenario 2 — Docker container or WSL (MCP server accessible from host network):
# MCP server listens on ALL interfaces so the host can reach it
# JADX plugin is still on the same machine
uv run jadx_mcp_server.py --http --host 0.0.0.0
Scenario 3 — JADX-GUI running on a different machine (e.g., remote VM):
# MCP server runs locally, but connects to JADX plugin on a remote machine
uv run jadx_mcp_server.py --http --jadx-host 192.168.1.100
Scenario 4 — Full remote setup (everything on different machines):
# MCP server listens on all interfaces on port 9999
# JADX plugin is on a different machine at 192.168.1.100:8652
uv run jadx_mcp_server.py --http --host 0.0.0.0 --port 9999 --jadx-host 192.168.1.100 --jadx-port 8652
[!CAUTION]
⚠️ Security Warning — Remote Binding
When using
--host 0.0.0.0(or any non-localhost address), the MCP server binds to all network interfaces over plain HTTP with no authentication. This means:
- Anyone on the network can connect and invoke all MCP tools
- There is no TLS encryption — traffic can be intercepted
- An attacker can use the server to read decompiled code, rename classes/methods, and access debug info
Mitigations:
- Only bind to
0.0.0.0on trusted, isolated networks (e.g., Docker bridge, local VM)- Use a firewall to restrict access to the MCP port
- Consider an SSH tunnel instead:
ssh -L 8651:127.0.0.1:8651 remote-hostSimilarly,
--jadx-hostwith a non-localhost address means the MCP server will make unauthenticated HTTP requests to that host. Ensure the target is trusted.
MCP-aware apps connect directly. For everything else that speaks POST /v1/chat/completions —
OpenRouter, LiteLLM, vLLM, Ollama's OpenAI layer, OmniRoute, … — examples/openai_compatible_client.py
is a reference adapter: it connects to a running jadx_mcp_server.py --http, converts the MCP tool list
into OpenAI function-calling tools, and runs the call → execute → feed-back loop until the model answers.
# terminal 1
uv run jadx_mcp_server.py --http --host 127.0.0.1 --port 9000
# the example needs the openai SDK; the server itself does not
pip install -r examples/requirements.txt
# OpenAI
OPENAI_API_KEY=sk-... python examples/openai_compatible_client.py \
--prompt "What does com.example.app.MainActivity do?"
# a local gateway (any placeholder key works)
OPENAI_BASE_URL=http://127.0.0.1:11434/v1 OPENAI_API_KEY=ollama OPENAI_MODEL=llama3.1 \
python examples/openai_compatible_client.py
# show the tool schema the model is offered, without calling a model at all
python examples/openai_compatible_client.py --list-tools
--base-url, --api-key and --model (or the OPENAI_BASE_URL / OPENAI_API_KEY / OPENAI_MODEL
environment variables) point it at any provider. --max-steps caps how many tool rounds a question may
take and --max-tool-chars truncates a single result, so one large class dump cannot blow the model's
context. Run it without --prompt for an interactive session.
Add Support for apktool
Add support for hermes code (ReactNative Application)
Add docker support
Add more useful MCP Tools
Make LLM be able to modify code on JADX
Add prompts templates, give llm access to Android APK Files as Resources
Build MCP Client to support Local LLM
END-GOAL : Make all android reverse engineering and APK modification tools Connect with single MCP server to make reverse engineering apk files as easy as possible purely from vibes.
The files related to JADX-AI-MCP can be found here
The files related to jadx-mcp-server can be found in this repository only.
This project is a plugin for JADX, an amazing open-source Android decompiler created and maintained by @skylot. All core decompilation logic belongs to them. I have only extended it to support my MCP server with AI capabilities.
The original README.md from jadx is included here in this repository for reference and credit.
This MCP server is made possible by the extensibility of JADX-GUI and the amazing Android reverse engineering community.
Also huge thanks to @aaddrick for developing Claude desktop for Debian based linux.
And in last thanks to @anthropics for developing the Model Context Protocol and @FastMCP team
And all open source maintainers and contributors that makes libraries and dependencies which allows project like this possible.
Thank you Mseep.net for auditing and providing Assessment Badge.
This project uses following awesome libraries.
Plugin - Java
MCP Server - Python
This plugin inherits the Apache 2.0 License from the original JADX repository.
Disclaimer
The tools jadx-ai-mcp and jadx_mcp_server are intended strictly for educational, research, and ethical security assessment purposes. They are provided "as-is" without any warranties, expressed or implied. Users are solely responsible for ensuring that their use of these tools complies with all applicable laws, regulations, and ethical guidelines.
By using jadx-ai-mcp or jadx_mcp_server, you agree to use them only in environments you are authorized to test, such as applications you own or have explicit permission to analyze. Any misuse of these tools for unauthorized reverse engineering, infringement of intellectual property rights, or malicious activity is strictly prohibited.
The developers of jadx-ai-mcp and jadx_mcp_server shall not be held liable for any damage, data loss, legal consequences, or other consequences resulting from the use or misuse of these tools. Users assume full responsibility for their actions and any impact caused by their usage.
Use responsibly. Respect intellectual property. Follow ethical hacking practices.
Built with ❤️ for the reverse engineering and AI communities.
MCP server for JADX-AI Plugin
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Jadx se ejecuta localmente por stdio.
Última comprobación: 2026-10-26. MCP server for JADX-AI Plugin
