How mritunjaysingh04/rea-reverse-engineer-anything-with-bots works
REA is a local reverse-engineering MCP server with a CLI sharing its analysis workflows. An agent or terminal user selects a target and asks REA to inspect or trace it; REA routes work to target-specific analysis engines and returns findings with evidence and limitations. The map preserves the documented native, application, browser, Android, firmware, and binary-diagnostics capabilities. Some subsystem paths are directories because their implementation files were not sampled; relationships without direct source or README evidence are omitted.
Main entry points: ReverseEngineeringService.ts Reverse analysis · main.ts MCP server · registerReverseEngineeringTools.ts MCP tool routes · reverseEngineeringCommands.ts CLI commands
Components 22
Entry points
- MCP server
src/main.ts - MCP tool routes
src/server/registerReverseEngineeringTools.ts - CLI commands
src/cli/reverseEngineeringCommands.ts
Analysis workflow
- Reverse analysis
src/application/reverse/ReverseEngineeringService.ts - Provider composition
src/composition/reverseEngineering.ts - Analysis contracts
src/domain/reverseEngineering.ts
Analysis providers
- Native providers
src/ghidra/GhidraProviderClient.ts - Hopper provider
src/hopper/HopperClient.ts - IDA provider
src/ida/IdaSessionClient.ts - Debugger sessions
src/gdb/GdbSessionManager.ts - Rizin debugger
src/rizin/RizinDebugSessionManager.ts - Cutter bridge
src/cutter/CutterBridgeClient.ts
Target capabilities
- Binary diagnostics
src/application/binaryDiagnostics - JavaScript analysis
src/javascript/analysis/JavaScriptAnalysisWorker.ts - Browser observation
src/browser - Android analysis
src/application/android - Firmware analysis
src/application/firmware
Evidence and results
- Evidence model
src/domain/evidence.ts - Typed analysis errors
src/domain/analysisErrorBase.ts
Other components
- AI agent
- Terminal user
- Local target
Connections 22
- AI agent → MCP server: asks via MCP
README.md - Terminal user → CLI commands: runs workflows
README.md - MCP server → MCP tool routes: registers tools
src/server/registerReverseEngineeringTools.ts - MCP tool routes → Reverse analysis: invokes
src/server/registerReverseEngineeringTools.ts - CLI commands → Reverse analysis: creates service
src/cli/reverseEngineeringCommands.ts - Reverse analysis → Provider composition: uses commands
src/composition/reverseEngineering.ts - Reverse analysis → Analysis contracts: validates inputs
src/application/reverse/ReverseEngineeringService.ts - Local target → Reverse analysis: supplies target
README.md - Reverse analysis → Evidence model: retains findings
src/domain/evidence.ts - Reverse analysis → Typed analysis errors: reports failures
src/application/reverse/ReverseEngineeringService.ts - Provider composition → Native providers: selects provider
- Reverse analysis → Binary diagnostics: analyzes layout
- Reverse analysis → JavaScript analysis: analyzes app
- Reverse analysis → Browser observation: observes runtime
- Reverse analysis → Android analysis: analyzes package
- Reverse analysis → Firmware analysis: analyzes firmware
- Native providers → Local target: inspects binaries
README.md - Hopper provider → Local target: inspects binaries
README.md - IDA provider → Local target: inspects binaries
README.md - Debugger sessions → Local target: debugs target
- Rizin debugger → Local target: debugs target
- Cutter bridge → Local target: analyzes binary