Cheatengine Bridge MCP Server
Analyze program memory and debug game structures using AI-driven automation.
Data last scanned today · Reviewed today
Overview
The Cheatengine Bridge MCP Server acts as an interface between your AI agents and Cheat Engine, enabling direct interaction with running process memory. It accelerates reverse engineering and security research by automating tasks like pointer chain resolution, AOB signature generation, and C++ object identification through RTTI. By leveraging the MCP protocol, you can offload complex memory inspection tasks to an AI, transforming hours of manual hex dump analysis into rapid conversational queries. The system utilizes a Python-based MCP server that communicates with a Lua worker thread inside Cheat Engine, providing access to memory addresses, disassembly, and debugging tools.
Our verdict
With a security score of 50/100, this tool is categorized as high risk. The high-risk designation stems from the lack of editorial review and the uncertainty surrounding its read-only mode and authentication methods. This tool is intended for advanced users performing security audits or reverse engineering who are comfortable managing the security implications of interfacing an AI agent with live process memory and debug-level operations.
- Zero direct dependencies minimize supply-chain surface area
- Active development with a recent commit three days ago
- Supported by a community of seven active contributors
- Released under the permissive MIT license
- Security mechanisms like read-only mode remain unreviewed
- Authentication methods have not undergone independent security evaluation
- Lacks an official vendor maintenance status
- No external homepage provides additional project context
Tools
| Tool | Description | Risk |
|---|---|---|
| read_memory | Read any data type from memory. | low |
| read_integer | Read an integer value from memory. | low |
| read_string | Read a string value from memory. | low |
| read_pointer_chain | Follow pointer chains like [[base+0x10]+0x20]. | low |
| scan_all | Find values in memory. | low |
| aob_scan | Find byte patterns in memory. | low |
| disassemble | Disassemble memory into instructions. | low |
| analyze_function | Perform code analysis on a function. | low |
| dissect_structure | Auto-detect fields and types of a memory structure. | low |
| get_rtti_classname | Identify C++ object types using RTTI. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Is this server compatible with non-Windows operating systems?
The native named pipe transport is Windows-only because it relies on pywin32. However, you can use the TCP relay transport to run the MCP server on Linux, inside a container, or on a remote machine.
›What software prerequisites are required for the server?
You need Python 3.10+ installed. For native Windows setups, the server requires the mcp and pywin32 packages.
›How do I connect the MCP server to Cheat Engine?
You must execute the ce_mcp_bridge.lua script within Cheat Engine to establish the bridge. This can be done via the 'Execute Script' menu or by adding a dofile line to your Cheat Table Lua script.
›Does the server support remote connections via TCP?
Yes, you can use the ce_tcp_relay.py script on the Windows host to relay commands. This allows the MCP server to communicate with Cheat Engine over a TCP socket instead of a local named pipe.
›Are there any specific configuration requirements for using DBVM tools?
If you intend to use DBVM tools, you must explicitly enable DBVM within Cheat Engine before running the bridge script.
›Are there security considerations for using the TCP relay?
Yes, anyone who can reach the relay port can control your Cheat Engine instance. You should only bind the relay to trusted network interfaces.
Badge
Maintain this server? Add the live badge to your README.