Skip to main content
Glama
bethington

Ghidra MCP Server

by bethington

Related Servers

Alternatives to Ghidra MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Large Language Models to interact with Binary Ninja for reverse engineering tasks like viewing assembly code, decompiled code, renaming functions, and adding comments.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A headless Ghidra server that enables AI agents to perform deep reverse-engineering tasks such as disassembly, decompilation, and patching via the Model Context Protocol. It supports extensive automation of analysis workflows in sandboxed environments through a catalog of over 200 specialized tools.
      196
      GPL 2.0

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools mostly have distinct purposes: group lifecycle management, tool discovery/status, instance management, and file import. There is some potential overlap between search_tools, check_tools, and list_tool_groups because all relate to discovering or checking tools, but the descriptions clarify when each should be used.

    Naming Consistency5/5

    All tools use snake_case with a clear verb_noun pattern: load_tool_group, unload_tool_group, check_tools, search_tools, import_file, list_instances, connect_instance. Singular/plural differences such as load_tool_group versus list_tool_groups are semantically appropriate rather than inconsistent.

    Tool Count5/5

    The eight listed tools form a well-scoped static bridge layer for connection, import, and tool-group management. Additional Ghidra analysis tools are loaded dynamically, so the static count is appropriate rather than bloated.

    Completeness4/5

    The static surface covers instance discovery/connect, binary import, tool-group loading/unloading, and tool search/check. Core reverse-engineering operations are not in this static list but become available after connecting and loading groups; minor lifecycle gaps such as explicit disconnect or program close/save remain.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week