Let Billion-Dollar AI Datacenters Parse Your Hex Dumps
It exposes Cheat Engine’s ~180 debugging and memory-analysis primitives as MCP tools so Claude, Cursor, or Copilot can reverse-engineer binaries via natural language instead of manual clicking.

What it does
This project is a protocol bridge that lets MCP-compatible AI agents control Cheat Engine through natural language. You describe what you want—“find the packet decryptor hook” or “resolve this pointer chain”—and the agent invokes the appropriate Lua-backed tool, reading memory, disassembling functions, or setting hardware breakpoints on your behalf. It turns the traditional days-long manual reverse-engineering workflow into a conversational back-and-forth.
The interesting bit
The bridge exposes roughly 180 discrete MCP tools, from basic read_memory and aob_scan to kernel-mode DBVM tracing and on-the-fly C compilation into shellcode. The architecture is deliberately simple—JSON-RPC over a named pipe (or an optional TCP relay for remote setups)—which means the AI is literally calling dissect_structure and get_rtti_classname as functions in its own context.
Key highlights
- ~180 tools covering memory scanning, pointer resolution, structure dissection, disassembly, breakpoint management, process control, and even window input automation.
- TCP relay mode lets the MCP server run outside Windows (WSL, containers, remote hosts) while Cheat Engine stays local.
- Auto-generates update-resistant AOB signatures and can identify C++ object types via RTTI.
- Ships with extensive AI context documentation and task briefings so agents can self-direct parallel workers.
Caveats
- Native named-pipe transport is Windows-only; cross-platform use requires the TCP relay workaround.
- The README explicitly warns that leaving Cheat Engine’s “Query memory region routines” setting enabled causes
CLOCK_WATCHDOG_TIMEOUTBSODs during protected-page scans. - Shell execution tools are gated behind an opt-in environment variable because arbitrary code execution is a genuine risk.
Verdict
Grab this if you are a reverse engineer, game modder, or security researcher who already lives in Cheat Engine and wants to automate the tedious parts. Skip it if you expect a polished standalone product—it is glue code, albeit very capable glue, between two complex ecosystems.
Frequently asked
- What is miscusi-peek/cheatengine-mcp-bridge?
- It exposes Cheat Engine’s ~180 debugging and memory-analysis primitives as MCP tools so Claude, Cursor, or Copilot can reverse-engineer binaries via natural language instead of manual clicking.
- Is cheatengine-mcp-bridge open source?
- Yes — miscusi-peek/cheatengine-mcp-bridge is open source, released under the MIT license.
- What language is cheatengine-mcp-bridge written in?
- miscusi-peek/cheatengine-mcp-bridge is primarily written in Lua.
- How popular is cheatengine-mcp-bridge?
- miscusi-peek/cheatengine-mcp-bridge has 1.4k stars on GitHub and is currently holding steady.
- Where can I find cheatengine-mcp-bridge?
- miscusi-peek/cheatengine-mcp-bridge is on GitHub at https://github.com/miscusi-peek/cheatengine-mcp-bridge.