ReversePort

ReversePort

Reverse engineer anything. Port it anywhere.

The reverse-engineering and porting toolkit for AI coding agents.

Read Godot packs, Unity IL2CPP, .NET and native binaries, compare builds, keep proof for every claim — and port games between Godot, Unity, Unreal and three.js with parity checks.

npx reverseport setup

A real run on Godot's 2D platformer demo , JSON trimmed to the key fields. Watch the MP4 .

Used ReversePort on something? Show us what you ported · ⭐ Star the repo if it saved you time.

Website · Quick start · What's new · Every agent · Prompts · How it compares · FAQ · Contributing · Docs

English · Nederlands

---

See a feature you like in an app or a game? Ask your agent how it works — down to the decompiled function — and then ask it to build your own version. Have a game in Godot and want it in Unity? Ask your agent to port it, unit by unit, verified. No files at all? Give it a name or a store page.

ReversePort gives agents one consistent way to do all of that:

• 🎮 Game formats built in — Godot .pck (also inside the .exe) and .gdc/.scn/.res back to an editable project, Unity asset bundles and .assets (textures as PNG, meshes as OBJ, audio, scripts in use), Unity IL2CPP global-metadata.dat, .unitypackage, GameMaker, Ren'Py, RPG Maker, Unreal .pak, FMOD and Wwise banks; it also recognises Quake PAK, Doom WAD, XNB and VPK. No engine install needed.
• 🔍 Understand anything — engine and version of any project or exported game, dependency graphs, scenes, symbols in 30+ languages, executables, packs and unknown data. JS/TS monorepos (pnpm, Turborepo, Nx, Lerna, Rush, tsconfig paths, #imports, Deno import maps) and Rust workspaces resolve too. No build step, no dependencies.
• 🧠 Go deep — decompile, cross-reference and trace native, managed (.NET), Android, Electron/JavaScript, WebAssembly, firmware and browser targets through Ghidra, Hopper, IDA, JADX and more. ReversePort connects to the tools you have installed, drives them and shows the evidence behind every conclusion.
• 🔀 Compare builds — what changed between build 43 and 44: files, packs and .NET types and methods, biggest changes first.
• 🧾 Proof, not guesses — a proof case ties every claim to saved evidence and keeps unknowns visible. In Claude Code, guard hooks stop a "done" while a proof case fails its check.
• 🧩 Rebuild precisely — no files? A name, a store page or a website is enough for a clean-room rebuild spec: every system, the parameters to measure, a parity table and a project skeleton.
• 🚚 Port for real — Godot ⇄ Unity, Godot → Unreal, Godot → three.js, GDScript → C#, Godot 3 → 4, RPG Maker → Godot, or language to language. Scenes and transforms convert automatically; code is ported by your agent with API maps; port_verify and port_trace prove nothing was left behind and behaviour matches.
• 🔒 Local — runs on your machine. Targets are only read; output goes to new folders. Nothing is uploaded to an analysis service, there is no telemetry and no extra API bill.

Quick start

1. Connect your agent

With Node.js 22.23.4 or newer (24.22.1+ on Node 24):

npx reverseport setup

Pick your agents, review the changes and approve. Setup registers one MCP server and installs the matching skill, with backups of existing configuration. Restart your agent afterwards. Setup supports Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more agents; other clients can use manual MCP registration.

Claude Code plugin

Instead of setup for Claude Code — includes the server, the porting skills, the port-architect agent and the guard hooks; do not use both:

/plugin marketplace add laaielichter/reverseport

/plugin install reverseport@reverseport

The plugin asks for its settings once (deep-analysis engine on or off, tool list size, workspace folder, your Ghidra folder). The same marketplace also offers the sister plugins stashpad@reverseport and agentdisk@reverseport.

From source

git clone https://github.com/laaielichter/reverseport && cd reverseport

npm ci && npm run build ./bin/reverseport.mjs setup

The recon, build-inspection, lookup, blueprint and porting commands already work right after git clone, with no install at all: node bin/reverseport.mjs scan ./MyGame.

2. Ask your agent

What is ./MyGame made with? Show me the evidence, then plan a port to Unity.

That's it. The agent picks the tools; you get answers with the evidence behind them.

What's new

1.16 — first contributions from the community:

• Workspace names that start with two dots work now. Thanks @bfs2021 (#112)!

1.15 — Unity bundles and one server name everywhere:

• re_archive unpacks Unity asset bundles and .assets files: textures as PNG, meshes as OBJ, audio, text and the scripts in use.
• The MCP server is now called reverseport in every client, so tools are mcp__reverseport__*. Breaking: rerun reverseport setup (or reverseport update) and update permission rules that name mcp__rea__*.
• Sturdier on Windows: CRLF patches, TEMP/TMP and host variables in the isolated verifiers.

1.14 — ready for the Claude plugin directory, with a slim claude-directory branch.

1.12 — more formats (Doom WAD, WAD2/WAD3, XNB, VPK), more game libraries in re_scan, monorepo globs and import maps, and a Godot → three.js walkthrough.

Every release is in the changelog.

Works with every agent

Connect through MCP, HTTP, vendor APIs or the shell. See Connect any agent for integration and runtime behaviour.

Skills

Workflow skills teach the agent which tool comes next. See the skill catalogue and guard hooks.

Prompts to try

Start with a question about your project or a port. See example prompts and a complete porting sequence.

What it does

Inspect projects and builds, reconstruct behaviour and port between engines. See supported targets, prerequisites and porting routes.

CLI

Run the same workflows from your shell and receive JSON results; see game and porting examples and the full CLI reference. For engine selection, see Choose a provider.

Tools

One MCP server serves the recon, build, proof and porting tools. See the tool overview and generated contracts.

How it compares

If you live inside IDA or Ghidra all day, a dedicated server for that tool goes deepest there. ReversePort's deep-analysis engine is REA; if you want broad reverse engineering without the game formats, porting and proof cases, REA itself is a good choice too.

FAQ

Is this legal? Use it on software you own or are allowed to analyse. ReversePort does not decrypt, crack or bypass DRM, anti-cheat or licensing. See RESPONSIBLE-USE.md.

Does it upload my files? No. It runs on your machine, only reads the target and writes output to new folders. There is no telemetry; PRIVACY.md lists the few times it uses the network.

Where do I get it? Only from npm as reverseport, the MCP Registry as io.github.laaielichter/reverseport, or this repository. Copies under other names are not ours.

Does it port my code automatically? Scenes, transforms and assets convert automatically. Code is written by your agent, one unit at a time, with an API map for the engine pair; port_verify then checks for leftovers, missing functions and dormant logic (stub bodies, functions nothing calls, silenced warnings), so a port that "compiles" but does nothing is not reported as done.

Do I need Ghidra? Only for decompiling native binaries. ReversePort finds Ghidra, Hopper or IDA but never installs them. Scanning, packs, IL2CPP metadata, build diffs, lookup, blueprints and porting need nothing extra.

How is this different from REA? REA is the dee