Star on GitHubStar1.1k stars

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.

Targets
App
Category
Independent MCP integrations
Relationship
Independent agent integration
Sources reviewed

Requirements & limits

  • 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.

About this entry

The description was reviewed against primary sources.

Report an outdated entry Suggest a translation fix

Primary sources

  1. README.md GitHub · zinja-coder/apktool-mcp-server · Revision 12bb331
  2. apktool_mcp_server.py GitHub · zinja-coder/apktool-mcp-server · Revision 12bb331
  3. pyproject.toml GitHub · zinja-coder/apktool-mcp-server · Revision 12bb331
  4. LICENSE GitHub · zinja-coder/apktool-mcp-server · Revision 12bb331
  5. https://github.com/zinja-coder/apktool-mcp-server/releases/tag/V3.0.2

More in Apps

All 174 entries in Apps

↑↓ move↵ open⌘↵ new tab