Cheat Engine MCP Bridge
Let multibillion $ AI datacenters analyze the program memory for you.
Create mods, trainers, security audits, game bots, accelerate RE, or do anything else with any program and game in a fraction of a time.
The Problem
You're staring at gigabytes of memory. Millions of addresses. Thousands of functions. Finding that one pointer, that one structure takes days or weeks of manual work.
What if you could just ask?
"Find the packet decryptor hook."
"Find the OPcode of character coordinates."
"Find the OPcode of health values."
"Find the unique AOB pattern to make my trainer reliable after game updates."
That's exactly what this does.
- Stop clicking through hex dumps and start having conversations with the memory.
What You Get:
| Before (Manual) | After (AI Agent + MCP) |
|---|---|
| Day 1: Find packet address | Minute 1: "Find RX packet decryption hook" |
| Day 2: Trace what writes to it | Minute 3: "Generate unique AOB signature to make it update persistent" |
| Day 3: Find RX hook | Minute 6: "Find movement OPcodes" |
| Day 4: Document structure | Minute 10: "Create python interpreter of hex to plain text" |
| Day 5: Game updates, start over | Done. |
Your AI can now:
- Read any memory instantly (integers, floats, strings, pointers)
- Follow pointer chains:
[[base+0x10]+0x20]+0x8→ resolved in ms - Auto-analyze structures with field types and values
- Identify C++ objects via RTTI: "This is a CPlayer object"
- Disassemble and analyze functions
- Debug invisibly with hardware breakpoints + Ring -1 hypervisor
- And much more!
How It Works
flowchart TD
AI[AI Agent: Claude/Cursor/Copilot]
AI -->|MCP Protocol - JSON-RPC over stdio| MCP
MCP[mcp_cheatengine.py - Python MCP Server]
MCP <-->|Named Pipe - Async| PIPE
PIPE["\\.\\pipe\\CE_MCP_Bridge_v99"]
PIPE <--> CE
subgraph CE[Cheat Engine - DBVM Mode]
subgraph LUA[ce_mcp_bridge.lua]
WORKER[Worker Thread - Blocking I/O]
MAIN[Main Thread - GUI + CE API]
WORKER <-->|Sync| MAIN
end
end
MAIN -->|Memory Access| TARGET[Target .exe]
Installation
pip install -r MCP_Server/requirements.txt
Or manually:
pip install mcp pywin32
Quick Start
1. Load Bridge in Cheat Engine
1. Enable DBVM in CheatEngine.
2. File → Execute Script → Open ce_mcp_bridge.lua → Execute
Look for: [MCP v11.4.0] Server started on \\.\pipe\CE_MCP_Bridge_v99
2. Configure MCP Client
Add to your MCP configuration (e.g., mcp_config.json):
{
"servers": {
"cheatengine": {
"command": "python",
"args": ["C:/path/to/MCP_Server/mcp_cheatengine.py"]
}
}
}
Restart the IDE to load the MCP server config.
3. Verify Connection
Use the ping tool to verify connectivity:
{"success": true, "version": "11.4.0", "message": "CE MCP Bridge Active"}
4. Start Asking Questions
"What process is attached?"
"Read 16 bytes at the base address"
"Disassemble the entry point"
43 MCP Tools Available
Memory
| Tool | Description |
|---|---|
read_memory, read_integer, read_string |
Read any data type |
read_pointer_chain |
Follow [[base+0x10]+0x20] paths |
scan_all, aob_scan |
Find values and byte patterns |
Analysis
| Tool | Description |
|---|---|
disassemble, analyze_function |
Code analysis |
dissect_structure |
Auto-detect fields and types |
get_rtti_classname |
Identify C++ object types |
find_references, find_call_references |
Cross-references |
Debugging
| Tool | Description |
|---|---|
set_breakpoint, set_data_breakpoint |
Hardware breakpoints |
start_dbvm_watch |
Ring -1 invisible tracing |
And many more at AI_Context/MCP_Bridge_Command_Reference.md
Critical Configuration
BSOD Prevention
Example Workflows
Finding a value:
You: "Scan for gold: 15000" → AI finds 47 results
You: "Gold changed to 15100" → AI filters to 3 addresses
You: "What writes to the first one?" → AI sets hardware BP
You: "Disassemble that function" → Full AddGold logic revealed
Understanding a structure:
You: "What's at [[game.exe+0x1234]+0x10]?"
AI: "RTTI: CPlayerInventory"
AI: "0x00=vtable, 0x08=itemCount(int), 0x10=itemArray(ptr)..."
Project Structure
MCP_Server/
├── mcp_cheatengine.py # Python MCP Server (FastMCP)
├── ce_mcp_bridge.lua # Cheat Engine Lua Bridge
└── test_mcp.py # Test Suite
AI_Context/
├── MCP_Bridge_Command_Reference.md # MCP Commands reference
├── CE_LUA_Documentation.md # Full CheatEngine 7.6 official documentation
└── AI_Guide_MCP_Server_Implementation.md # Full technical documentation for AI agent
Testing
Running the test:
python MCP_Server/test_mcp.py
Expected output:
✅ Memory Reading: 6/6 tests passed
✅ Process Info: 4/4 tests passed
✅ Code Analysis: 8/8 tests passed
✅ Breakpoints: 4/4 tests passed
✅ DBVM Functions: 3/3 tests passed
✅ Utility Commands: 11/11 tests passed
⏭️ Skipped: 1 test (generate_signature)
────────────────────────────────────
Total: 36/37 PASSED (100% success)
The Bottom Line
You no longer need to be an expert. Just ask the right questions.
⚠️ EDUCATIONAL DISCLAIMER
This code is for educational and research purposes only. It's created to show the capabilities of the Model Context Protocol (MCP) and LLM-based debugging. I do not condone the use of these tools for malicious hacking, cheating in multiplayer games, or violating Terms of Service. This is a demonstration of software engineering automation.
Metadata
Release files for iflow-mcp_miscusi-peek-cheatengine-mcp-bridge 11.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0.tar.gz | 5.7 kB | Without provenance | Details for iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0-py3-none-any.whl |
Total release size: 11.8 kB
Release files / iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0.tar.gz
| Download URL | iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5058217f78b073e9a4ae5f0ec74c657651449c8b3ab461403821c254432ecaad
|
|
BLAKE2b-256 checksum How to use checksums |
2c23b53a5f03bd7c09067263befedbd57fe87032032cae783425ae3e331a44bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0-py3-none-any.whl
| Download URL | iflow_mcp_miscusi_peek_cheatengine_mcp_bridge-11.4.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9400f814c0dd59815b4d93f500529b48b441f5e2c8e18e76841ac4eb334072b
|
|
BLAKE2b-256 checksum How to use checksums |
cbc8386439bb936ce7fb7146115a9a8557ebac73ababbe8cbb62819ebf1e6d39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_miscusi-peek-cheatengine-mcp-bridge 11.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.