Skip to main content
hc
Submit
mcpSource-backed

Ghidra MCP Server by bethington

Apache-licensed Ghidra MCP bridge with GUI and headless workflows for binary analysis, decompilation, scripting, debugger access, batch operations, and Ghidra Server collaboration.

by bethington · submitted by oktofeesh1·added 2026-06-05·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/bethington-ghidra-mcp-server
Source URLs
https://github.com/bethington/ghidra-mcp/blob/main/README.md, https://github.com/bethington/ghidra-mcp
Brand
Ghidra MCP
Brand domain
github.com
Safety notes
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.
Privacy notes
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.
Author
bethington
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

35 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

2 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime2Permissions & scopes2Review & approval135 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes.

5 areas
  • SafetyPermissions & scopesUse this server only for binaries and systems you are authorized to inspect, debug, emulate, modify, document, or reverse engineer.
  • SafetyExecution & processesThe tool surface includes write-capable operations such as renaming, typing, commenting, label changes, script execution, structure creation, and project/version-control workflows.
  • SafetyExecution & processesUnknown binaries, malware samples, debugger targets, and imported scripts can be dangerous; isolate analysis environments and avoid running untrusted code on a primary workstation.
  • SafetyGeneralHeadless, Docker, CI, and Ghidra Server workflows can affect shared repositories or automated pipelines if configured with write access.
  • SafetyExecution & processesKeep human review on operations that change analysis state, scripts, project metadata, or shared Ghidra Server content.
  • PrivacyLocal filesTool 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.
  • PrivacyCredentials & tokensReverse engineering projects often contain proprietary firmware, customer binaries, vulnerability findings, credentials embedded in samples, exploit indicators, and private research notes.
  • PrivacyExecution & processesMCP client logs, model transcripts, Ghidra project history, Docker volumes, CI logs, and Ghidra Server repositories may retain sensitive analysis data.
  • PrivacyCredentials & tokensDo not commit private binaries, generated Ghidra projects, debugger traces, analysis exports, credentials, proprietary symbols, or customer-specific reverse engineering notes.

Safety notes

  • 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.

Privacy notes

  • 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.

Prerequisites

  • Ghidra 12.1 or a compatible version installed and available on the local machine or analysis host.
  • Java 21, Maven 3.9 or newer, Python 3.10 or newer, and Python package installation available.
  • Ghidra extension deployment permissions for the user profile or headless environment.
  • Authorization to analyze the binaries, firmware, traces, symbols, and shared Ghidra projects loaded into the tool.
  • Review of script execution, debugger, Ghidra Server, Docker, and headless-analysis settings before use.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
35 minutes
Difficulty
advanced
Full copyable content
{
  "mcpServers": {
    "ghidra-bethington": {
      "command": "python",
      "args": ["GHIDRA_MCP_REPO/bridge_mcp_ghidra.py"]
    }
  }
}

About this resource

Content

Ghidra MCP Server by bethington is a Ghidra extension and Python MCP bridge for authorized reverse engineering workflows. It exposes Ghidra analysis context to MCP clients so an agent can inspect decompilation output, cross-references, symbols, strings, data structures, memory, P-code, debugger state, project metadata, scripts, comments, labels, and batch analysis operations.

This entry covers the separate bethington/ghidra-mcp project. The catalog also includes LaurieWired's GhidraMCP server, which is a different repository and implementation. Choose between them based on the Ghidra version, setup path, tool surface, transport, and workflow style your reverse engineering task needs.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository, README, license, security policy, bridge script, Maven build metadata, Python requirements, example MCP config, Docker files, and release page for current Ghidra compatibility, setup, transports, build steps, and safety guidance.

Features

  • Bridge MCP clients to Ghidra through a Python bridge and Java extension.
  • Inspect decompiled functions, call graphs, references, strings, memory, imports, exports, symbols, and data types.
  • Perform write-capable analysis updates such as renaming, typing, comments, labels, and structure work.
  • Run Ghidra scripts and automate repeatable reverse engineering workflows.
  • Use batch operations for larger analysis passes.
  • Work with P-code emulation and debugger-oriented workflows.
  • Run in GUI, headless, Docker, or CI-oriented analysis environments.
  • Integrate with Ghidra Server project and version-control workflows.

Installation

Clone the repository and run the setup preflight against your Ghidra install:

git clone https://github.com/bethington/ghidra-mcp.git
cd ghidra-mcp
python -m tools.setup preflight --ghidra-path GHIDRA_INSTALL_DIR

Then install prerequisites, build, and deploy the extension:

python -m tools.setup ensure-prereqs --ghidra-path GHIDRA_INSTALL_DIR
python -m tools.setup build
python -m tools.setup deploy --ghidra-path GHIDRA_INSTALL_DIR

Enable the Ghidra plugin, open an authorized project, and configure your MCP client to run bridge_mcp_ghidra.py.

Use Cases

  • Ask Claude to explain functions from a loaded Ghidra project.
  • Summarize strings, imports, exports, references, and call graph neighborhoods.
  • Generate consistent comments, names, and type improvements for reviewed functions.
  • Investigate data structures and field usage in firmware or malware samples.
  • Run repeatable documentation workflows across related binaries.
  • Use headless or Docker analysis jobs for CI-style reverse engineering pipelines.
  • Coordinate Ghidra Server project workflows with shared analysis teams.

Safety and Privacy

Reverse engineering tools can touch sensitive and dangerous material. Use an isolated analysis environment, especially for unknown binaries, malware, debugger sessions, scripts, and CI/headless jobs. Keep human approval on any operation that writes comments, names, types, labels, structures, scripts, version-control state, or shared project data.

Treat binary metadata and analysis output as sensitive. Decompiled code, strings, paths, hashes, symbols, debugger state, memory reads, comments, and Ghidra project data can reveal proprietary software internals, vulnerability findings, customer artifacts, credentials embedded in samples, and private research notes.

Duplicate Check

No bethington/ghidra-mcp entry or matching source URL was found in content/mcp. The existing LaurieWired/GhidraMCP entry covers a separate Ghidra MCP repository and implementation.

#reverse-engineering#ghidra#security#debugger#binary-analysis

Source citations

Add this badge to your README

Show that Ghidra MCP Server by bethington is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/bethington-ghidra-mcp-server.svg)](https://heyclau.de/entry/mcp/bethington-ghidra-mcp-server)

How it compares

Ghidra MCP Server by bethington side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
Ghidra MCP Server by bethington

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
GhidraMCP Server

Ghidra plugin and MCP bridge that lets AI assistants inspect, decompile, rename, comment, and analyze binaries through Ghidra reverse-engineering workflows.

Open dossier
IDA Pro MCP Server

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 AI MCP Server

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
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand————
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorbethingtonLaurieWiredmrexodiazinja-coder
Added2026-06-052026-06-052026-06-052026-06-05
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓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 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.✓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✓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, 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.✓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
  • Ghidra 12.1 or a compatible version installed and available on the local machine or analysis host.
  • Java 21, Maven 3.9 or newer, Python 3.10 or newer, and Python package installation available.
  • Ghidra extension deployment permissions for the user profile or headless environment.
  • Authorization to analyze the binaries, firmware, traces, symbols, and shared Ghidra projects loaded into the tool.
  • Installed Ghidra.
  • Python 3.
  • MCP Python SDK dependencies required by the project.
  • Latest GhidraMCP release zip imported as a Ghidra extension.
  • IDA Pro 8.3 or newer, with IDA Pro 9 recommended; IDA Free is not supported.
  • Python 3.11 or newer and uv.
  • Globally activated idalib for the headless Claude Code plugin path.
  • Supported MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, or another documented host.
  • Java 11 or newer and JADX-GUI installed.
  • Python and uv available for installing or running the companion MCP server.
  • The JADX AI MCP plugin installed in JADX-GUI.
  • An Android APK, JADX project, or reverse-engineering target you are authorized to analyze.
Install
git clone https://github.com/bethington/ghidra-mcp.git && cd ghidra-mcp && python -m tools.setup preflight --ghidra-path GHIDRA_INSTALL_DIR
python bridge_mcp_ghidra.py --transport sse
claude plugin marketplace add mrexodia/claude-marketplace && claude plugin install ida-pro-mcp@mrexodia
jadx plugins --install "github:zinja-coder:jadx-ai-mcp"
Config
Manual-only setup:
python -m tools.setup preflight --ghidra-path GHIDRA_INSTALL_DIR
python -m tools.setup ensure-prereqs --ghidra-path GHIDRA_INSTALL_DIR
python -m tools.setup build
python -m tools.setup deploy --ghidra-path GHIDRA_INSTALL_DIR
{
  "mcpServers": {
    "ghidra": {
      "command": "python",
      "args": ["/ABSOLUTE_PATH_TO/bridge_mcp_ghidra.py"]
    }
  }
}
{
  "mcpServers": {
    "ida-pro": {
      "command": "uv",
      "args": ["run", "idalib-mcp", "--stdio"]
    }
  }
}
{
  "mcpServers": {
    "jadx-mcp-server": {
      "command": "jadx_mcp_server"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by YB0y

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Claude Code in Regulated Finance Environments

Deploy Claude Code in security-sensitive finance environments.

Added 8mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JSONbored

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.