RHEXA

Installation

Development status: RHEXA is not yet published as a package. It is installed from source. The command and the MCP server are called rhexa.

Prerequisites

ComponentVersionPurpose
Operating systemLinux x64 (tested: Ubuntu 22.04, also under WSL2)macOS and Windows follow with the platform verification runs
Node.js and npm22.22.2+, 24.15+ or 26+agent layer
JDK25 (LTS), 64-bit, full JDKRhexa Engine
Git, Python 3, GCC/Clang, makecurrent versionsbuilding agent layer and engine
ps (procps)system packageprocess ownership checks on Linux

Optional tools such as a Chrome browser for web analysis, jadx for Android or Frida for runtime observation are only needed for those analyses.

1. Install the agent layer

git clone https://github.com/mjanda0815/reengineering.git rhexa
cd rhexa
npm ci
npm run build:cached
npm link        # provides the "rhexa" command

The repository is currently private; access has to be granted.

2. Install the Rhexa Engine

You need a 64-bit JDK 25, reachable through JAVA_HOME or PATH. RHEXA then downloads the engine itself:

export JAVA_HOME=/path/to/jdk-25
rhexa engine install

The command shows the download URL, size, SHA-256 and target directory and asks before it writes anything (--yes skips the question, --dry-run only shows the plan). It checks size and checksum against the published manifest and installs to ~/.local/share/rhexa/engine. Archives are currently published for Linux x86-64. rhexa engine status shows which engine RHEXA uses, rhexa engine languages lists the processor languages it can analyze, rhexa engine remove removes it.

Build the engine yourself (developers)
cd engine
./gradlew -I gradle/support/fetchDependencies.gradle
./gradlew buildGhidra
unzip build/dist/rhexaengine_*_linux_x86_64.zip -d ~/opt
export GHIDRA_INSTALL_DIR="$HOME/opt/rhexaengine_12.1.4_DEV"

GHIDRA_INSTALL_DIR takes precedence over the installed engine.

3. Check

rhexa doctor

4. Connect your agent

RHEXA speaks the Model Context Protocol (MCP) and works with MCP-capable agents. For Claude Code, register the server like this (adjust the paths):

claude mcp add --scope user rhexa \
  -e JAVA_HOME=/path/to/jdk-25 \
  -- node /path/to/rhexa/scripts/rhexa.mjs mcp

RHEXA finds the installed engine itself; no engine path is needed.

Other agents expect an entry with the command node and the arguments /path/to/rhexa/scripts/rhexa.mjs mcp in their MCP configuration.

Important: rhexa setup registers the npm package rhexa-agents, which is not published yet. Register RHEXA as shown above. An installation of the original REA (rea, npm rea-agents) can stay next to it.

Restart your agent afterwards and continue with getting started.