Using Ghidra with REA (MCP)

For native binaries, REA can drive an existing Ghidra installation as one of its analysis providers. REA does not download or upgrade Ghidra or Java for you — you install those outside REA, then point environment variables at absolute paths.

Upstream documents a bring-your-own Ghidra path (typically Ghidra 12.1.x with a 64-bit JDK 21+) on supported Linux/macOS hosts. After exporting GHIDRA_INSTALL_DIR and JAVA_HOME, run doctor then setup, for example:

export GHIDRA_INSTALL_DIR=/absolute/path/to/ghidra_PUBLIC
export JAVA_HOME=/absolute/path/to/jdk-21
npx -y rea-agents@latest doctor --provider ghidra --json
npx rea-agents@latest setup

Replace both paths with your installations. Restart the agent after setup so the MCP registration is loaded. If tools do not appear, reconnect the client and re-run doctor --provider ghidra --json — the report names the failed check.

Scope reminder. Use Ghidra + REA only on artifacts you are authorized to reverse engineer. This site will not publish crack workflows or DRM bypasses. Full install notes: /docs/install/. Upstream: installation.