Ghidra MCP Server
Related Servers
Alternatives to Ghidra MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn 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
- AlicenseBqualityFmaintenanceA Model Context Protocol server for IDA interaction and automation. This server provides tools to read IDA database via Large Language Models.19549MIT
- AlicenseNot gradedqualityDmaintenanceExposes Ghidra headless binary analysis capabilities via the Model Context Protocol, enabling AI assistants to decompile, analyze, and emulate binaries with 32 tools and multi-binary support.2MIT
- AlicenseNot gradedqualityDmaintenanceA 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.3MIT
- AlicenseNot gradedqualityCmaintenanceA 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.196GPL 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with IDA Pro for reverse engineering and binary analysis tasks.12103MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.