Skip to main content
Glama
bethington

Ghidra MCP Server

by bethington
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Ghidra MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Binary Ninja MCP Server

      rsprudencio
      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

    • Ghidra Headless MCP

      mrphrazer
      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.
      172
      GPL 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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: connection management, importing, tool group operations, and searching. There is no functional overlap, making it clear which tool to use for each task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., connect_instance, import_file, load_tool_group), making them predictable and easy to understand.

    Tool Count5/5

    With 8 tools, the server covers the essential operations for managing Ghidra instances and tool groups without being excessive or insufficient for the stated purpose.

    Completeness4/5

    The set covers core workflows: connection, import, tool group lifecycle, and search. A minor gap is the lack of an explicit disconnect tool, but switching instances effectively covers that, making the surface largely complete.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources