Integration
apktool-mcp-server
Python MCP server that drives a local Apktool install so agents can decode APKs; list, read, search and edit smali and resource files; read AndroidManifest.xml and apktool.yml; and rebuild the project.
Requirements and limitations
- Apktool must be installed and available on PATH. Reviewed release: V3.0.2, published 2026-07-02 and identical to the default branch at review. Run it with uv; the README and script header state Python 3.10+, while pyproject.toml declares >=3.13. Apache-2.0.
- MCP is served over stdio by default, or over streamable HTTP on port 8652 with --http. The README lists 13 tools; the reviewed script also registers health_check, analyze_project_structure and get_workspace_info. Project paths must stay inside the workspace directory (apktool_mcp_server_workspace by default).
- modify_smali_file, modify_resource_file, clean_project and build_apk change the decoded project, so work on copies; the modify tools keep timestamped backups by default. As with Apktool, rebuilding an APK is distinct from recovering original Java source.
About this entry
- Type
- Integration
- Category
- Independent MCP integrations
- Relationship
- Independent agent integration
- Targets
- App
Sources reviewed
The description was reviewed against primary sources. This does not establish runtime testing, security auditing or verified compatibility.
Primary sources
- https://github.com/zinja-coder/apktool-mcp-server/blob/12bb33134af905923a0a58643dcc35fd694ad6f6/README.md
- https://github.com/zinja-coder/apktool-mcp-server/blob/12bb33134af905923a0a58643dcc35fd694ad6f6/apktool_mcp_server.py
- https://github.com/zinja-coder/apktool-mcp-server/blob/12bb33134af905923a0a58643dcc35fd694ad6f6/pyproject.toml
- https://github.com/zinja-coder/apktool-mcp-server/blob/12bb33134af905923a0a58643dcc35fd694ad6f6/LICENSE
- https://github.com/zinja-coder/apktool-mcp-server/releases/tag/V3.0.2