Apktool MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check the health status of the APKTool MCP server and APKTool installation. Returns: Dictionary containing server status and APKTool availability |
| decode_apkC | Decode an APK file using APKTool with comprehensive validation and error handling. |
| build_apkB | Build an APK file from a decoded APKTool project with enhanced validation. |
| get_manifestB | Get the AndroidManifest.xml content from a decoded APK project with validation. |
| get_apktool_ymlA | Get apktool.yml information from a decoded APK project with validation. |
| list_smali_directoriesC | List all smali directories in a project with enhanced metadata. |
| list_smali_filesA | List smali files with pagination support and enhanced filtering. |
| get_smali_fileC | Get content of a specific smali file by class name with validation. |
| modify_smali_fileB | Modify smali file content with validation and backup support. |
| list_resourcesC | List resources with pagination support and enhanced metadata. |
| get_resource_fileB | Get content of a specific resource file with validation and metadata. |
| modify_resource_fileB | Modify the content of a specific resource file with validation and backup support. |
| search_in_filesC | Search for patterns in files with pagination and enhanced filtering. |
| clean_projectA | Clean a project directory to prepare for rebuilding with enhanced backup support. |
| analyze_project_structureB | Analyze the structure of a decoded APK project and provide comprehensive metadata. |
| get_workspace_infoA | Get information about the APKTool MCP server workspace and current projects. Returns: Dictionary with workspace information and project list |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct action or resource type (e.g., decode vs build, smali vs manifest vs resources). There is no ambiguity between tools; even list tools separate directories, files, and resources clearly.
All tool names follow a consistent verb_noun pattern with lowercase and underscores. Verbs like get, list, modify, build are used predictably, making the naming scheme uniform and easy to navigate.
16 tools cover the core APK decoding, building, analysis, and modification workflows without being excessive. The count is well-scoped for the domain and each tool serves a distinct purpose.
The set covers primary CRUD operations for resources and smali files, plus decode/build/analyze. A minor gap is the lack of a modify_apktool_yml tool, but overall the surface is comprehensive for typical APKTool tasks.