Hosting

Local JADX GUI plugin plus local Python MCP process; the server connects to the running GUI plugin over localhost HTTP.

Transport

stdio by default; optional local Streamable HTTP mode.

Endpoint

Local process; no hosted endpoint documented

Authentication

No external account or key is documented for the default local setup. The local MCP server communicates with the JADX plugin at localhost port 8650 by default. HTTP mode has no authentication; the project warns against binding to non-localhost networks without isolation and access controls.

Requirements

• JADX GUI 1.5.1 or newer and Java 11 or newer for the current plugin docs.
• Python 3.10 or newer and uv for the standalone MCP server.
• An Android APK opened in JADX GUI for meaningful analysis.
• Install both the JADX AI plugin and MCP server components from the official releases or documented repositories.

Setup steps

1. Install JADX GUI 1.5.1 or newer and Java 11 or newer. In a terminal with the JADX CLI available, install the community plugin with `jadx plugins --install "github:zinja-coder:jadx-ai-mcp"`; alternatively follow the official guide to download the release jar and install it through the GUI.
2. Install uv, then install the Python server with `uv tool install git+https://github.com/zinja-coder/jadx-mcp-server`. The official docs also describe cloning the server repo and running `uv run jadx_mcp_server.py`.
3. Configure a local stdio MCP process with command `jadx_mcp_server` after the uv tool install. Start JADX GUI, load an APK, and ensure the plugin is active; the MCP server connects to the plugin at 127.0.0.1:8650 by default.
4. Reconnect the MCP client and inspect tools/list. Begin with read-only calls such as `get_android_manifest`, `get_main_activity_class`, or `get_class_source`. Rename and add-comment tools modify the JADX project; obtain user approval before using them.
5. Avoid `--host 0.0.0.0` on untrusted networks: the optional HTTP mode has no authentication or TLS and can expose decompiled code and project-modifying operations.

The official README names 29 tools. This catalog includes the documented tool list; no live tools/list response was obtained. Several tools can rename classes, methods, fields, packages, or variables and add comments to the JADX project.

• fetch_current_class

  Get the selected class name and complete source.

  01
• get_selected_text

  Read the currently selected text in JADX.

  02
• get_all_classes

  List classes in the open project.

  03
• get_class_source

  Read source for a named class.

  04
• get_method_by_name

  Read source for a named method.

  05
• search_method_by_name

  Search for a method across classes.

  06
• search_classes_by_keyword

  Search class source by keyword with pagination.

  07
• get_methods_of_class

  List methods in a selected class.

  08
• get_fields_of_class

  List fields in a selected class.

  09
• get_smali_of_class

  Read smali for a class.

  10
• get_main_activity_class

  Find the main activity class declared by the manifest.

  11
• get_main_application_classes_code

  Read main application class code based on the manifest package.

  12
• get_main_application_classes_names

  List main application class names based on the manifest package.

  13
• get_android_manifest

  Read AndroidManifest.xml.

  14
• get_manifest_component

  Read a selected manifest component.

  15
• get_strings

  Read strings.xml.

  16
• get_all_resource_file_names

  List resource file names.

  17
• get_resource_file

  Read the content of a resource file.

  18
• rename_class

  Rename a class in the open JADX project.

  19
• rename_method

  Rename a method in the open JADX project.

  20
• rename_field

  Rename a field in the open JADX project.

  21
• rename_package

  Rename a package in the open JADX project.

  22
• rename_variable

  Rename a variable within a method.

  23
• add_comment

  Add or update a comment on a class, method, field, or source line in the JADX project.

  24
• list_comments

  List comments stored in the project.

  25
• debug_get_stack_frames

  Read debugger stack frames.

  26
• debug_get_threads

  Read debugger thread state.

  27
• debug_get_variables

  Read debugger variables.

  28
• xrefs_to_class

  Find references to a class, with pagination.

  29
• xrefs_to_method

  Find references to a method, with pagination.

  30
• xrefs_to_field

  Find references to a field, with pagination.

  31

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• This is a community integration for JADX and must not be presented as an official JADX server.
• Requires an open JADX GUI with the plugin installed and an APK loaded; the standalone MCP process does not provide decompilation on its own.
• Some tools mutate the open JADX project by renaming symbols or adding comments; use only after approval.
• Optional HTTP mode is unauthenticated plain HTTP; keep it on localhost or an isolated trusted network.
• The selected logo is the official JADX product logo, not a mark implying that the community MCP is maintained by JADX's owner.
• Documentation and logo were reviewed; connection, tools/list, and functionality were not tested.

• community repository documentation

  Documents the community plugin and server relationship, install commands, runtime prerequisites, localhost plugin connection, 29 tool names, and read versus mutating capabilities.

• community server repository

  Documents the standalone Python stdio server install and command, plus local HTTP mode and binding/security options.

• official upstream product repository

  JADX project repository lists the selected standalone JADX product logo asset. This is used as the product logo for the integration, while the publisher field remains the community plugin author.

• discovery directory

  JADX AI MCP appeared in the awesome-mcp.tools mobile/security search results; directory data was used for discovery only.

• maintainer or vendor documentation

  Maintainer docs describe the plugin/server split and a 29-tool catalog; existing 31 count requires reconciliation and remains partial.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.