ghidra-mcp
Related Servers
Alternatives to ghidra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server and Ghidra plugin for reverse engineering, enabling clients like Claude to control Ghidra. Adds a run_python tool to execute arbitrary Jython scripts server-side.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes Ghidra reverse engineering capabilities via MCP, enabling LLMs and agents to analyze binaries, decompile, search, and edit programs headlessly or with GUI integration.427Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI tools to execute IDA Python code inside IDA Pro for reverse engineering tasks via MCP over SSE.3-
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to autonomously reverse engineer applications by exposing Ghidra decompilation, renaming, and analysis tools to MCP clients.Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI agents and automation to perform Ghidra reverse-engineering tasks through MCP, including decompilation, live debugging, P-code emulation, data-flow analysis, and headless script execution, with specialized AArch64-aware emulation.8Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA PyGhidra-based MCP server that exposes Ghidra's reverse engineering capabilities to AI agents, enabling binary analysis via tools like overview, search, view, list, edit, script execution, and version control.1-
TDQS
Scored across 24 tools
Each tool targets a distinct reverse-engineering concern such as renaming, decompiling, cross-references, type editing, or vtable recovery. The main ambiguities are the overlapping information-retrieval roles of labels, address_info, and xrefs, plus the fact that create_function can also trigger disassembly.
Most tools use readable lowercase snake_case verb or verb_noun names like rename, create_function, set_types, and list_instructions. However, the pattern is inconsistent: several query tools are bare nouns (labels, xrefs, namespaces, vtable) and the get/list prefixes vary, so no strict convention is maintained.
At 24 tools, this is on the heavy side and beyond the typical well-scoped 3-15 tool range. The breadth is justifiable for a Ghidra automation server, but some tools such as rename_batch and vtable are specialized additions rather than core necessities.
The tool surface covers the main reverse-engineering workflow well: disassembly, decompilation, renaming, references, memory/data inspection, type management, classes/vtables, analysis, and search. Minor gaps such as byte patching/assembling and a dedicated delete tool are workable around because clear() can remove most artifacts.