Skip to main content
Glama
zinja-coder

Apktool MCP Server

by zinja-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Apktool MCP Server

No user-submitted related servers found.

    Related Servers

    • jadx-rpc

      AsherDLL
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for analyzing Android APK, DEX, or JAR files via a headless jadx engine, enabling LLM agents to query decompiled code, symbols, call graphs, and more.
      2
      GPL 3.0

    • JADX-MCP-SERVER

      bartest5
      A
      license
      Not graded
      quality
      C
      maintenance
      Fully automated MCP server built to communicate with JADX-AI-MCP Plugin to analyze Android APKs using LLMs like Claude — uncover vulnerabilities, parse manifests, and reverse engineer effortlessly.
      1
      Apache 2.0

    • Kawaiidra MCP

      wagonbomb
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that integrates Ghidra for binary analysis, enabling decompilation, disassembly, and advanced reverse engineering tasks through Claude Code.
      15
      MIT

    • ghidraMCP

      albertlab0
      A
      license
      Not graded
      quality
      D
      maintenance
      An Model Context Protocol server that enables LLMs to autonomously reverse engineer applications by exposing Ghidra's decompilation and analysis tools. It allows AI agents to list code structures, rename methods, and analyze binaries directly through MCP-compatible clients.
      Apache 2.0

    • GhidraMCP

      DaCodeChick
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that allows LLMs to autonomously reverse engineer applications using Ghidra, exposing tools like decompilation, renaming, and listing methods.
      27
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources