Practical overview
When it fits
Use it when an MCP-compatible LLM client needs to communicate with JADX-AI Plugin for Android APK inspection, either on the same machine or across separately configured hosts.
Who it is for
- Android developers who want an LLM client to inspect APKs through JADX.
- Mobile-security practitioners building assistant-supported APK review workflows.
- Developers integrating JADX-based analysis into an MCP client setup.
Documented uses
- Connect an MCP client to JADX-AI Plugin.
- Ask an LLM to help parse APK manifests and review applications for vulnerabilities.
- Support reverse-engineering workflows and access APK files as resources.
- Use documented JADX tools that allow an LLM to modify code in the analysis environment.
Requirements & limits
The repository is public and identifies the project as open source under the Apache-2.0 license. The README lists Python 3.10+ and Java 11+.
- The server and JADX-AI Plugin are separate components, with independent host and port settings.
- HTTP transport is an option; stdio is the default according to the CLI documentation.
- The README warns that remote HTTP binding is unauthenticated and unencrypted, and recommends restricting network access or considering an SSH tunnel.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect a local MCP server to the JADX-AI plugin over HTTP
Start the MCP server on the same machine and connect it to a local JADX plugin.
Before you start
- Python 3.10+
- A running JADX-AI-MCP plugin on the same machine; the documented default plugin address is 127.0.0.1:8650.
Steps
From the server project environment, start it with the command below.
uv run jadx_mcp_server.py --httpConnect an MCP client to the server at its documented default listener, 127.0.0.1:8651.
Expected outcome
The MCP server listens locally over HTTP and is configured to contact the JADX plugin at its default local address.
Guide limitations
- HTTP on localhost is documented; non-localhost binding is unauthenticated and unencrypted, and should be limited to trusted, isolated networks.
Configure the MCP server for a remote JADX plugin
Run the MCP server locally while directing it to a JADX plugin on another machine.
Before you start
- Python 3.10+
- A reachable JADX-AI-MCP plugin host; the example uses 192.168.1.100 with the default plugin port 8650.
Steps
Start the server with the command below.
uv run jadx_mcp_server.py --http --jadx-host 192.168.1.100Connect an MCP client to the server's default listener, 127.0.0.1:8651.
Expected outcome
The MCP server listens on its default local address and targets the plugin host specified by `--jadx-host`.
Guide limitations
- Requests to a non-localhost
--jadx-hostuse unauthenticated HTTP; use only a trusted target.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- zinja-coder/jadx-mcp-server · Official homepage title · retained in its source language

