Data as of

apktool-mcp-server for VS Code: Setup & Config

VS Code: apktool-mcp-server exposes APK decoding, inspection, editing, and rebuilding through MCP.

What you can do with apktool-mcp-server in VS Code

Pick it for an Apktool-backed MCP workflow spanning manifest review, smali edits, and APK rebuilding.

  • Review Android manifests and declared permissions
  • Read or update decoded resource files

Before you start: apktool-mcp-server in VS Code

  • Python 3.10 or later
  • uv
  • Apktool installed and available in the environment
  • A local project checkout or release download

Uses the Cherry Studio stdio example. Replace the project-directory placeholder. The README offers uv pip install httpx fastmcp if dependencies need manual installation.

apktool-mcp-server VS Code configuration

  1. Choose VS Code configuration scope

    For apktool-mcp-server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add apktool-mcp-server to VS Code

    Use the apktool-mcp-server entry below in servers. Keep apktool-mcp-server's documented stdio connection fields and your other VS Code entries.

  3. Check apktool-mcp-server in VS Code

    apktool-mcp-server: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "apktool-mcp-server": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "--directory",
        "path/to/apktool-mcp-server",
        "run",
        "apktool_mcp_server.py"
      ],
      "env": {}
    }
  }
}

apktool-mcp-server tools available to VS Code

apktool-mcp-server's stored tool list documents 13 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

build_apk

Look for build_apk among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

get_manifest

Look for get_manifest among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

Read the decoded Android manifest.

get_apktool_yml

Look for get_apktool_yml among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

Inspect Apktool project metadata.

list_smali_directories

Look for list_smali_directories among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

Enumerate smali directories in a decoded project.

list_smali_files

Look for list_smali_files among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

List smali files with an optional package-prefix filter.

get_smali_file

Look for get_smali_file among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

modify_smali_file

Look for modify_smali_file among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

list_resources

Look for list_resources among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

Enumerate decoded resources, optionally by type.

get_resource_file

Look for get_resource_file among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

Read a selected decoded resource.

modify_resource_file

Look for modify_resource_file among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

Change a selected resource file.

search_in_file

Look for search_in_file among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

clean_project

Look for clean_project among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

decode_apk

Look for decode_apk among VS Code's agent-mode tools after starting apktool-mcp-server through the MCP controls.

apktool-mcp-server: full stored tool descriptions

Troubleshooting apktool-mcp-server in VS Code

  • Make uv available in the workspace, container, or remote environment hosting apktool-mcp-server. Start through VS Code's MCP controls; inspect output and trust prompts.
  • apktool-mcp-server uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires a separately installed Apktool environment
  • Known limitation: Client testing is reported for Claude Desktop, with others pending
  • Known limitation: Usage is restricted to authorized analysis
  • General VS Code troubleshooting lives in the /clients/vscode guide.

apktool-mcp-server — details. VS Code guide

Frequently asked questions

For apktool-mcp-server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's apktool-mcp-server example uses stdio.

apktool-mcp-server's VS Code configuration invokes uv.

apktool-mcp-server's stored list contains 13 tools, including build_apk, get_manifest, get_apktool_yml. Compare those names with VS Code's connected tool list; the stored list is not a live check.

Yes. build_apk builds from a decoded Apktool project, and clean_project prepares the project for rebuilding.

The README requires downloading and configuring Apktool separately.