cheatengine-mcp-bridge and cheat-engine-server-python
These are competitors offering different approaches to the same goal: one prioritizes full automation of reverse engineering tasks through direct Cheat Engine integration, while the other emphasizes safety and structured read-only access to memory analysis, forcing users to choose based on whether they need unrestricted functionality or controlled security.
About cheatengine-mcp-bridge
miscusi-peek/cheatengine-mcp-bridge
Connect Cursor, Copilot & Claude directly to Cheat Engine via MCP. Automate reverse engineering, pointer scanning, and memory analysis using natural language.
Implements a Lua-based worker thread in Cheat Engine that communicates via named pipes to a Python MCP server, exposing 43 tools for memory inspection, pointer chain resolution, RTTI analysis, and hardware breakpoint debugging. Requires DBVM mode and specifically targets reverse engineering workflows by translating natural language queries into low-level memory operations—structure dissection, AOB pattern generation, and function disassembly—without manual hex dump navigation.
About cheat-engine-server-python
bethington/cheat-engine-server-python
MCP Cheat Engine Server — provides safe, structured read-only access to memory analysis and debugging functionality through the Model Context Protocol (MCP). For developers, security researchers, and game modders.
Exposes memory analysis tools (pattern scanning, pointer chain resolution, assembly disassembly) through MCP's stdio transport, integrating with Claude Desktop via structured JSON configuration. Enforces read-only access with process whitelisting and comprehensive operation logging, while supporting multiple data types and Cheat Engine table imports for reverse engineering workflows.
Scores updated daily from GitHub, PyPI, and npm data. How scores work