Ghidra plugin and MCP bridge that lets AI assistants inspect, decompile, rename, comment, and analyze binaries through Ghidra reverse-engineering workflows.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup.
Safety & privacy surface
4 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes, network access, third-party handling.
{
"mcpServers": {
"ghidra": {
"command": "python",
"args": ["/ABSOLUTE_PATH_TO/bridge_mcp_ghidra.py"]
}
}
}GhidraMCP is a Ghidra extension and MCP bridge for AI-assisted reverse engineering. It exposes Ghidra functionality to MCP clients so an assistant can inspect binaries, decompile functions, list methods, list classes, review imports and exports, rename methods and data, and build analysis notes.
The project includes a Ghidra plugin and a Python bridge that connects MCP clients to the Ghidra plugin's local server. Its README documents default local ports and optional bridge arguments for Claude Desktop, Cline, and 5ire.
These sources were reviewed on 2026-06-05. Prefer the live repository and release page for the current extension zip, bridge arguments, default ports, and client-specific setup instructions.
Install the latest GhidraMCP release zip as a Ghidra extension, restart Ghidra, and enable the GhidraMCP plugin under Ghidra's developer tools.
For a Claude Desktop-style local bridge:
{
"mcpServers": {
"ghidra": {
"command": "python",
"args": ["/ABSOLUTE_PATH_TO/bridge_mcp_ghidra.py"]
}
}
}
For clients that use SSE, run the Python bridge with the transport option and follow the repository's current instructions for host, port, and Ghidra server arguments.
python bridge_mcp_ghidra.py --transport sse
Use GhidraMCP only on binaries you are authorized to analyze. Treat unknown binaries and malware samples as hostile, and isolate the environment before opening them. Verify all agent-generated comments, names, and reports before saving or sharing them.
No LaurieWired/GhidraMCP entry or source URL was found in content/mcp. This
entry is separate from IDA Pro MCP and other security-analysis content.
Show that GhidraMCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/ghidramcp-server)GhidraMCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Ghidra plugin and MCP bridge that lets AI assistants inspect, decompile, rename, comment, and analyze binaries through Ghidra reverse-engineering workflows. Open dossier | Apache-licensed Ghidra MCP bridge with GUI and headless workflows for binary analysis, decompilation, scripting, debugger access, batch operations, and Ghidra Server collaboration. Open dossier | MCP server and Claude Code plugin for connecting IDA Pro or headless idalib to AI assistants for reverse engineering, decompilation, xref lookup, renaming, commenting, and binary analysis workflows. Open dossier | JADX plugin and companion Python MCP server that lets Claude inspect, search, refactor, and debug decompiled Android APKs from JADX-GUI. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | LaurieWired | bethington | mrexodia | zinja-coder |
| Added | 2026-06-05 | 2026-06-05 | 2026-06-05 | 2026-06-05 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Reverse engineering may be legally restricted; confirm authorization before analyzing third-party or proprietary binaries. Malware, exploit samples, and unknown binaries should be handled in isolated environments with limited network and filesystem access. LLM-generated names, comments, and conclusions must be verified against Ghidra decompiler output, disassembly, imports, exports, and xrefs. Keep backups of Ghidra projects before allowing an agent to rename symbols, alter comments, or save project state. | ✓Use this server only for binaries and systems you are authorized to inspect, debug, emulate, modify, document, or reverse engineer. The tool surface includes write-capable operations such as renaming, typing, commenting, label changes, script execution, structure creation, and project/version-control workflows. Unknown binaries, malware samples, debugger targets, and imported scripts can be dangerous; isolate analysis environments and avoid running untrusted code on a primary workstation. Headless, Docker, CI, and Ghidra Server workflows can affect shared repositories or automated pipelines if configured with write access. Keep human review on operations that change analysis state, scripts, project metadata, or shared Ghidra Server content. | ✓Reverse engineering may be legally or contractually restricted; confirm authorization before analyzing proprietary binaries or third-party samples. Malware samples and exploit tooling should be handled in isolated environments with network and filesystem controls. LLMs can hallucinate reverse-engineering conclusions; verify findings against disassembly, decompiler output, xrefs, and reproducible scripts. Do not let an agent patch, rename, comment, or save IDA databases used for evidence without review and backups. | ✓Use this server only for APKs and Android applications you own, are responsible for, or are explicitly authorized to inspect. The plugin exposes decompiled classes, methods, fields, smali, manifests, strings, resources, xrefs, and debugger state to the MCP client. Rename and refactor tools can modify JADX project state and naming decisions; review changes before saving project output or using generated reports. The architecture docs describe a local plugin service with no built-in authentication; keep it bound to localhost unless you add network controls. Optional HTTP mode for the MCP server should not be exposed to untrusted networks without authentication, TLS, and firewall restrictions. Decompiled strings, manifests, and resources can contain prompt-injection text or untrusted content; treat tool output as untrusted input. |
| Privacy notes | ✓Binaries, function names, strings, imports, exports, decompilation output, comments, and analysis notes may be sent to the MCP client and model. Extracted strings and decompiled code can expose proprietary logic, credentials, API endpoints, malware indicators, or customer data. Generated reports can reveal sensitive vulnerability research or product internals. | ✓Tool calls may expose binary names, file paths, hashes, strings, imports, exports, symbols, decompiled code, comments, type names, project names, repository URLs, debugger state, memory reads, and trace metadata. Reverse engineering projects often contain proprietary firmware, customer binaries, vulnerability findings, credentials embedded in samples, exploit indicators, and private research notes. MCP client logs, model transcripts, Ghidra project history, Docker volumes, CI logs, and Ghidra Server repositories may retain sensitive analysis data. Do not commit private binaries, generated Ghidra projects, debugger traces, analysis exports, credentials, proprietary symbols, or customer-specific reverse engineering notes. | ✓Binaries, IDA databases, symbol names, strings, comments, decompiler output, and vulnerability findings may be sent to the MCP client and model. Proprietary firmware, customer crash samples, malware indicators, license keys, and embedded secrets can appear in extracted strings or decompiled code. Reports and prompts may reveal unreleased product internals or sensitive security research. | ✓APK source, package names, manifests, resources, strings, selected text, debugger variables, and analysis prompts may be sent to the model provider. Debugger tools can expose runtime values, tokens, identifiers, device data, or user information from the analyzed application. Reverse-engineering work can reveal proprietary code, licensed assets, customer data, or confidential security findings. Avoid uploading malware samples, third-party apps, client applications, or regulated data to external model providers without approval. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude to Ghidra through a Python bridge and Java extension with decompiler, P-code, debugger, scripting, batch-edit, and headless analysis tools.
Connect Claude Code and other MCP clients to IDA Pro or idalib for assisted reverse engineering.
Source-backed guides for putting this to work.
Audit MCP client configuration before sharing it with a team.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.