repowiserepowise

MCP server

morluto / rea

Reverse engineer anything with agents, from app behavior down to native binaries.

★ 472,677stars on GitHubTypeScriptMIT

This connects Repowise to morluto/rea's code. It does not install rea.

Repowise maps public repos from their source. Not affiliated with morluto. What is Repowise?

github.com/morluto/reaIndexed at c0ee832

What is rea?

rea is a reverse-engineering toolkit that lets AI agents and terminal users inspect apps and binaries without their source code. It runs as an MCP server, a standard way for agents to call tools, and also as the rea command, and the tools return findings with their evidence. The project is written mainly in TypeScript. To install it, run npx rea-agents setup. Its code health is 8.2 out of 10 (Good), ranked #46 of 4,000+ indexed repos. The last commit to rea was on Nov 20, 2026, and 30 people have contributed.

As of commit c0ee832, indexed Nov 20, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentsrea.md

Repo facts: type, license, health, rank, contributors
rea facts
TypeMCP server
LicenseMIT
Code health8.2 / 10 (Good)
Health rank#46 of 4,000+ indexed repos
Last commitNov 20, 2026
Contributors30
Bus factor1
Size8,691 files, 2,042,595 lines

Install rea

Commands copied from the README

  1. 1With Node.js and npm installed, run the setup command.
    npx rea-agents setup

Releases on GitHub (latest rea-agents-6.10.1, Nov 20, 2026)

Full install notes on GitHub

Explore rea

Ask about this code in your agent

This connects Repowise to rea's code. It does not install rea. To install rea, use the install steps.

Useful if you want to change or fork rea: your agent can ask how it is put together and get answers that cite its files.

Ask about rea

Answers come from rea's README and source, with the files they cite. Two free answers a day without an account.

Featured answer

rea is a reverse-engineering toolkit that lets AI agents and terminal users inspect apps and binaries without their source code, and its tools return findings along with their evidence. It runs as an MCP server, a standard way for agents to call tools, and also as the rea command, and the same workflows are available as CLI commands. The project is written mainly in TypeScript and has 8691 files grouped into layers: Application with 1727 files, Service with 1082, Docs & Tooling with 1448, Types with 125, Config with 123, and CLI with 116. Tools are bound for agents in src/server/serviceToolBindings.ts, the src directory runs adb against Android devices, and the bridge directory exposes NativeAOT type metadata to Java and Swift, which a Ghidra extension loads through a descriptor. To start reading, begin with the entry points src/cli.ts, src/main.ts and scripts/rea.mjs, then check the scripts directory for packaged CLI checks and the website directory for the public documentation site.

Files per layer in rea6 layers.

Basis: Inferred · knowledge graph· as of c0ee832

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of morluto/rea from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

morluto/rea FAQ

What is rea?

rea is a reverse-engineering toolkit that lets AI agents and terminal users inspect apps and binaries without their source code. Its tools cover native binaries, Electron apps, Android APKs and Android devices.

How does rea work?

An agent calls rea through MCP, a standard way for agents to call tools, and rea returns findings with their evidence. The agent then uses those findings to ask follow-up questions, explain behavior, or write and test an implementation.

How do I install rea?

rea is installed by running npx rea-agents setup with Node.js and npm present. You then choose your agents, review the proposed changes, approve them, and restart your agent. See the install steps

What language is rea written in?

rea is written mainly in TypeScript. The repository also contains JavaScript, Python, Java, C and Swift files.

How is the rea code organized?

The src directory holds the main code, including the adb integration and server tool bindings. The bridge directory connects NativeAOT metadata to Java and Swift, and the website directory holds the public documentation site.

Who is rea for?

rea is for engineers who want to see how an existing feature works, and for building a similar one for their own project. It is used through AI agents or from the terminal.

What license does rea use?

rea uses the MIT license, identified as MIT in its repository metadata.

Code health

8.2out of 10Good

Hotspots average 6.4, the place fixes pay off most.

On the leaderboards:#20 of 66 TypeScript repos

Key features of rea

  • Sets up an agent with rea's MCP server and matching workflow instructions, keeping backups of existing configuration.
  • Analyzes native binaries through Hopper, Ghidra, IDA or Kuna, returning pseudocode, assembly, strings, symbols and references.
  • Inspects Electron and JavaScript applications, including modules, imports, source maps, routes, IPC and native add-ons.
  • Decompiles Android APKs through headless JADX, returning manifest declarations, classes and decompiled methods.
  • Advertises compact input schemas over MCP to reduce context overhead, while the full tool set and server-side validation stay unchanged.

How morluto/rea works

An agent calls rea through the MCP server, and the same workflows are also available as CLI commands. The entry points include src/cli.ts, src/main.ts and scripts/rea.mjs. src/server/serviceToolBindings.ts is one of the hotspot files in the server code, where tools are bound for agents to call. The src directory runs the adb command-line tool against Android devices and reads back its output. The bridge directory exposes NativeAOT type metadata to the Java and Swift sides, and a Ghidra extension loads it through a descriptor and calls its analyze method with the open program. The scripts directory holds checks for the packaged CLI and its integrations, and the website directory holds the public documentation site.

The codebase has 8,691 files and 52,180 symbols in 9 modules, led by TypeScript, JavaScript and Python. Code health is 8.2 out of 10, rated good.