rea.best简体中文 ↗
Home / Guides / Ghidra MCP server: using Ghidra through REA
REA / FIELD GUIDE

Ghidra MCP server: using Ghidra through REA

Prepare Ghidra for REA MCP: separate the Ghidra installation, JDK and agent registration, then check provider readiness before a native-binary investigation.

How a Ghidra MCP server relates to REA

Ghidra is an analysis engine; an MCP server makes tools available to an agent. Searches for Ghidra MCP Server can lead to several projects. This guide covers Ghidra through REA, not the configuration of every standalone Ghidra MCP integration.

Check whether your task needs Ghidra

For a JavaScript directory or supported ASAR, begin with our static case without adding a native engine. Prepare an appropriate engine when the investigation needs native-code, assembly or decompilation evidence.

Preparation checklist

  1. Prepare Ghidra and a full JDK using the upstream compatibility requirements. Check the OS and CPU architecture; a Java runtime alone may not be sufficient.
  2. Point GHIDRA_INSTALL_DIR at the real installation root and JAVA_HOME at a compatible JDK. An explicit invalid path is not corrected by automatic discovery.
  3. Run diagnostics, then preview setup for your selected client. Setup can preserve verified environment paths, but does not install Ghidra or Java for you.
npx rea-agents@6.5.0 doctor --json
npx rea-agents@6.5.0 providers --json

Why can the client connect while the engine is unavailable?

MCP registration tells the agent how to start REA. Engine readiness also depends on installation metadata, the headless launcher, the JDK and native decompiler components. GUI clients may inherit a different environment from a terminal. Inspect the paths recorded in setup, then check execution in that same client.

How to validate the first result

Use a small program you own and understand. Record its version, an input digest and one expected function. Check whether the output identifies that function, and inspect its evidence and limitations. Doctor passing is not analysis acceptance. We have not run this native Ghidra workflow here; our recorded case is JavaScript. Windows users should also check the upstream experimental-support notes.

Official Ghidra setup reference

Continue your investigation

Based on upstream REA documentation, reviewed October 17, 2026. Documentation-based guidance is not a live test of every client or target. Official setup reference · Project source and overview