Fetch the currently selected class and its code from the JADX-GUI plugin.

Kotlin compiler metadata (@Metadata / @DebugMetadata) is stripped by default; pass slim=False for a raw dump. Line numbering is unaffected.

Returns the currently selected text in the decompiled code view.

Fetch the source code of a method from a specific class.

Kotlin compiler metadata is stripped by default; pass slim=False for a raw dump.

Returns a list of all classes in the project with pagination support.

Fetch the Java source of a specific class.

Set with_line_numbers=True to get every line prefixed with its 1-based line number. Those are the numbers add_comment takes as its 'line' argument, so use this before placing a line comment instead of counting lines yourself.

Kotlin compiler metadata (@Metadata / @DebugMetadata) is stripped by default, which is where a large part of a Kotlin dump goes; the line numbers stay the same, so add_comment keeps working. Pass slim=False for a raw, unmodified dump.

Search for a method name across all classes.

List all method names in a class.

Search for classes containing a specific keyword with flexible filtering options.

This tool performs a comprehensive search across decompiled Android code, allowing you to:

1. Search within specific packages by providing a package name

2. Target specific search scopes (class names, method names, fields, code content, comments)

3. Combine multiple search scopes for precise results

Args: search_term: The keyword or string to search for. This is the main search query.

package (optional): Package name to limit the search scope.
    - If empty string (default), searches across all packages in the APK
    - If provided, only searches within classes belonging to the specified package
    - Example: "com.example.app" to search only in that package

search_in (optional): Comma-separated list of search scopes to target.
    Valid values:
    - "class": Search in class names only
    - "method": Search in method names only
    - "field": Search in field names only
    - "code": Search in code content (method bodies, statements, etc.)
    - "comment": Search in comments

    You can specify one or multiple scopes:
    - Single scope: "class" (only class names)
    - Multiple scopes: "class,method" (class names OR method names)
    - Combined: "class,method,code" (searches in all three scopes)

    Default: "code" (searches in code content)

offset (optional): Starting index for pagination. Default: 0
count (optional): Maximum number of results to return. Default: 20

Returns: dict: Paginated list of classes containing the search term, with metadata about matches

MCP Tool: search_classes_by_keyword Description: Advanced search tool that finds classes matching a keyword with package filtering and scope targeting capabilities. Use this when you need to find specific code patterns, class names, method names, or other identifiers across the decompiled APK.

List all field names in a class.

Fetch the smali representation of a class.

Retrieve specified component data from AndroidManifest.xml, support filter exported components. Support standard Android components: activity, provider, service, receiver.

Retrieve and return the AndroidManifest.xml content.

Retrieve contents of strings.xml files.

Retrieve all resource files names.

Retrieve resource file content.

Fetch main application classes' names from Manifest package.

Fetch main application classes' code with pagination.

Kotlin compiler metadata is stripped from every class by default; pass slim=False for raw dumps.

Fetch the main activity class from AndroidManifest.xml.

Kotlin compiler metadata is stripped by default; pass slim=False for a raw dump.

Get all packages in the APK sorted by class count. Shows total_classes, total_packages, and per-package name, class_count, is_likely_library. Use this first to understand the APK structure before searching.

Get decompilation cache statistics: hits, misses, hit_rate, cached_classes, compressed_mb, compression_ratio.

Clear the decompilation source cache and reset counters. Use when switching APKs or to free memory.

Renames a specific class.

Renames a specific method, optionally scoped to class_name.

Renames a specific field.

Renames a package and all its classes.

Renames a specific variable in a method.

Add a comment to decompiled code, shown in JADX-GUI and saved with the project.

Comment a class by passing only class_name, a method by also passing method_name (use method_signature such as '(I)V' to pick between overloads), or a field by passing field_name.

To comment a code line, pass line=N, the 1-based line number in the decompiled source of that class; get it from get_class_source(with_line_numbers=True) rather than counting lines. The comment is appended to the end of that line, and on a class, method or field declaration line it comments that declaration instead, matching what the comment shortcut does in JADX-GUI. Braces and blank lines have nothing to comment and are rejected, listing the nearest lines that work. Line numbers shift once a comment is added above, so re-read the source before addressing another line.

Every write is verified against the freshly decompiled code and the response echoes the rendered line, so there is no need to read the class back to check. A comment that does not render is rolled back and returns an error rather than being silently stored, which JADX itself does not detect.

A new comment on the same target replaces the previous one, so annotations can be refined without creating duplicates, and passing an empty comment removes it. style is one of LINE, BLOCK, BLOCK_CONDENSED, JAVADOC or JAVADOC_CONDENSED (default: LINE).

Use this to record what a class or method actually does while reverse engineering: the comments persist in the JADX project and are searchable later with search_classes_by_keyword(search_in="comment").

List the comments already stored in the project, optionally filtered to one class.

Each entry reports class_name, node_type (CLASS/METHOD/FIELD), node_id, comment and style. Use this before add_comment to see what is already annotated instead of re-deriving it.

Get current stack frames (call stack).

Get all threads in the debugged process.

Get current variables when process is suspended.

Find all references to a class.

Find all references to a method.

Find all references to a field.