apktool-mcp-server

Wraps the APKTool CLI to decompress and decompile Android APK binaries into human-readable smali (Jasmin) bytecode, AndroidManifest.xml, and resource files. The server maintains a workspace directory structure where each decoded APK becomes a distinct project, enabling LLMs to analyze and modify Android application internals through structured file access patterns rather than binary inspection.

Implements directory enumeration and file content retrieval for smali source files within decoded APK projects, with optional package-level filtering to reduce context noise. The server scans the smali/ directory tree and returns file listings or individual file contents, enabling LLMs to navigate Android application structure and locate specific classes or methods for analysis.

Exposes all 13 MCP tools through the standard Model Context Protocol with JSON schema definitions, enabling MCP clients (Claude Desktop, Cherry Studio, Ollama) to discover available tools and understand their parameters. The server implements the MCP tools list and tool call handling endpoints, allowing AI clients to invoke APK operations through natural language requests.

Maintains a centralized workspace directory (apktool_mcp_server_workspace/) where each decoded APK becomes an isolated project subdirectory. The server manages project naming, isolation, and lifecycle, enabling concurrent analysis of multiple APKs without cross-contamination. Projects are identified by name and persist across server restarts.

Implements the Model Context Protocol server using FastMCP framework with STDIO transport, enabling bidirectional JSON-RPC communication with MCP clients. The server reads tool invocation requests from stdin and writes responses to stdout, allowing integration with Claude Desktop, Cherry Studio, Ollama, and other MCP-compatible clients without network configuration.

Scans the smali/ directory tree of a decoded APK and returns hierarchical package structure with directory listings. The server maps Java package names to filesystem paths and provides directory enumeration at multiple levels, enabling LLMs to understand the APK's code organization and navigate to specific packages or classes.

Enables atomic read-modify-write operations on smali source files within a decoded APK project. The server accepts file path and new content, validates the smali syntax (basic checks), and writes modifications back to disk. This allows LLMs to patch vulnerabilities, inject logging, or modify application behavior by editing bytecode directly without requiring full recompilation.

Retrieves the decoded AndroidManifest.xml file from a project, exposing the application's declared permissions, activities, services, broadcast receivers, and intent filters. The server parses the XML and returns it in human-readable format, enabling LLMs to understand the app's security model, entry points, and declared capabilities without binary inspection.

Retrieves the apktool.yml configuration file generated during APK decoding, which contains metadata about the APK (version, SDK targets, framework resources, build configuration). This YAML file documents how APKTool decompiled the APK and what frameworks were used, enabling LLMs to understand the build context and compatibility constraints.

Invokes APKTool to recompile a modified project directory back into a signed APK binary. The server coordinates the rebuild process, handles APKTool CLI execution, and returns the path to the rebuilt APK. This enables LLMs to apply code modifications and generate testable APK artifacts without manual build tool invocation.

Prepares a decoded APK project for rebuilding by cleaning intermediate files and build artifacts generated by APKTool. The server removes build caches and temporary files that may interfere with rebuilding, ensuring a clean state for subsequent build operations. This is typically called before build_apk to guarantee consistency.

Enumerates and retrieves Android resource files (strings.xml, colors.xml, layouts, drawables, etc.) from the res/ directory of a decoded APK. The server provides directory listing and file content access, enabling LLMs to analyze resource definitions, UI layouts, and string constants without binary inspection.

Enables modification of Android resource files (XML-based resources like strings.xml, layouts, colors.xml) within a decoded APK project. The server accepts file path and new content, writes modifications back to disk, and allows LLMs to patch configuration, UI layouts, or string constants without recompiling smali code.

Implements regex-based or literal string search across all files in a decoded APK project (smali code, resources, manifests). The server scans the project directory tree and returns matching file paths and line numbers, enabling LLMs to locate specific code patterns, hardcoded values, or configuration strings without manual file traversal.