1. Home
  2. JADX-AI-MCP
  3. JADX-AI-MCP for VS Code: Setup & Config

Data as of

JADX-AI-MCP for VS Code: Setup & Config

VS Code: Connect an MCP assistant to JADX's live Android decompilation context.

What you can do with JADX-AI-MCP in VS Code

Choose it for assistant-assisted Android reverse engineering inside an active JADX session.

  • Review decompiled Android code for insecure API use or embedded secrets.
  • Rename obfuscated symbols during an investigation.

Before you start: JADX-AI-MCP in VS Code

  • Java 11 or newer
  • Python 3.10 or newer
  • JADX with the JADX-AI-MCP plugin installed
  • Companion JADX MCP Server
  • uv

This follows the README's Cherry Studio configuration. Replace the directory with the companion server checkout. The plugin and server are separate components; uv venv alone does not start the MCP server.

JADX-AI-MCP VS Code configuration

  1. Choose VS Code configuration scope

    For JADX-AI-MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add JADX-AI-MCP to VS Code

    Use the jadx-ai-mcp entry below in servers. Keep JADX-AI-MCP's documented stdio connection fields and your other VS Code entries.

  3. Check JADX-AI-MCP in VS Code

    JADX-AI-MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "jadx-ai-mcp": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "--directory",
        "path/to/jadx-mcp-server",
        "run",
        "jadx_mcp_server.py"
      ],
      "env": {}
    }
  }
}

JADX-AI-MCP tools available to VS Code

JADX-AI-MCP's stored tool list documents 29 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

fetch_current_class

Look for fetch_current_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_selected_text

Look for get_selected_text among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Retrieve text highlighted in the decompiler.

get_all_classes

Look for get_all_classes among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Enumerate classes in the opened project.

get_class_source

Look for get_class_source among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Load decompiled source for a named class.

get_method_by_name

Look for get_method_by_name among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Read a method's decompiled source.

search_method_by_name

Look for search_method_by_name among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Locate matching methods across classes.

search_classes_by_keyword

Look for search_classes_by_keyword among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Search class source for a keyword with paginated results.

get_methods_of_class

Look for get_methods_of_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Enumerate methods belonging to a class.

get_fields_of_class

Look for get_fields_of_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Enumerate a class's fields.

get_smali_of_class

Look for get_smali_of_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_main_activity_class

Look for get_main_activity_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_main_application_classes_code

Look for get_main_application_classes_code among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_main_application_classes_names

Look for get_main_application_classes_names among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_android_manifest

Look for get_android_manifest among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_manifest_component

Look for get_manifest_component among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

get_strings

Look for get_strings among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Load the packaged strings.xml resource.

get_all_resource_file_names

Look for get_all_resource_file_names among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Enumerate packaged resource filenames.

get_resource_file

Look for get_resource_file among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Read a selected resource file.

rename_class

Look for rename_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Change a class's displayed name.

rename_method

Look for rename_method among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Assign a clearer name to a method.

rename_field

Look for rename_field among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Change a field identifier.

rename_package

Look for rename_package among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

Rename an application package.

rename_variable

Look for rename_variable among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

debug_get_stack_frames

Look for debug_get_stack_frames among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

debug_get_threads

Look for debug_get_threads among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

debug_get_variables

Look for debug_get_variables among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

xrefs_to_class

Look for xrefs_to_class among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

xrefs_to_method

Look for xrefs_to_method among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

xrefs_to_field

Look for xrefs_to_field among VS Code's agent-mode tools after starting JADX-AI-MCP through the MCP controls.

JADX-AI-MCP: full stored tool descriptions

Troubleshooting JADX-AI-MCP in VS Code

  • Make uv available in the workspace, container, or remote environment hosting JADX-AI-MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
  • JADX-AI-MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires a plugin plus a separate Python server.
  • Known limitation: Remote setups must distinguish the MCP listener from the JADX plugin connection.
  • General VS Code troubleshooting lives in the /clients/vscode guide.

JADX-AI-MCP — details. VS Code guide

Frequently asked questions

For JADX-AI-MCP, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's jadx-ai-mcp example uses stdio.

JADX-AI-MCP's VS Code configuration invokes uv.

JADX-AI-MCP's stored list contains 29 tools, including fetch_current_class, get_selected_text, get_all_classes. Compare those names with VS Code's connected tool list; the stored list is not a live check.

No. The integration also uses a standalone Python MCP server that communicates with the plugin.

Yes. The documented tools retrieve stack frames, threads, and variables from JADX's debugger.