Loading...

ghidraMCP is a Model Context Protocol server that exposes Ghidra's reverse engineering tools to LLMs for autonomous binary analysis and modification.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
ghidraMCP is a Model Context Protocol server that exposes Ghidra's reverse engineering tools to LLMs for autonomous binary analysis and modification.
ghidraMCP's safety depends heavily on the configuration of both Ghidra and the MCP client. It is relatively safe when used in a controlled environment with limited network access and well-defined permissions. Risks increase when exposed to untrusted networks or when the MCP client has broad permissions within Ghidra.
Performance is limited by Ghidra's processing speed and the network latency between the MCP client and the Ghidra instance. Large binaries may take a significant amount of time to analyze.
Cost considerations include the computational resources required to run Ghidra and the potential cost of using a commercial LLM service as the MCP client.
{
"mcpServers": {
"ghidra": {
"command": "python",
"args": [
"/ABSOLUTE_PATH_TO/bridge_mcp_ghidra.py",
"--ghidra-server",
"http://127.0.0.1:8080/"
]
}
}
}Decompile and analyze binaries in GhidraDecompiles and analyzes binary files using Ghidra's capabilities.
Primarily a read operation, though analysis can trigger further actions.
Automatically rename methods and dataAutomatically renames methods and data within Ghidra's project based on LLM suggestions.
Modifies the Ghidra project, but changes are typically reversible.
List methods, classes, imports, and exportsLists methods, classes, imports, and exports from the analyzed binary.
Read-only operation that retrieves information about the binary.
None
cloud
ghidraMCP's safety depends heavily on the configuration of both Ghidra and the MCP client. It is relatively safe when used in a controlled environment with limited network access and well-defined permissions. Risks increase when exposed to untrusted networks or when the MCP client has broad permissions within Ghidra.
Autonomy is controlled by the capabilities of the connected LLM and the permissions granted within Ghidra. There is no built-in sandboxing or rollback mechanism.
Production Tip
Monitor Ghidra's resource usage and performance to prevent denial-of-service issues when using ghidraMCP in a production environment.
The default port is 8080, but it can be configured in Ghidra's tool options.
Theoretically, yes. However, compatibility may vary, and some clients may require specific configuration.
It depends on your security requirements and configuration. Exercise caution and monitor resource usage.
The plugin is designed for recent Ghidra versions. Check the release notes for specific compatibility information.
Verify that the Ghidra HTTP server is running, the port is correctly configured, and there are no firewall restrictions.
No, ghidraMCP does not implement authentication. Access control relies on Ghidra's internal mechanisms and network security.
No, ghidraMCP operates on the Ghidra project and does not directly modify the original binary file.