home / mcp / mcp cheat engine server
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.
Configuration
View docs{
"mcpServers": {
"bethington-cheat-engine-server-python": {
"command": "python",
"args": [
"server/main.py",
"--debug",
"--read-only"
]
}
}
}You can use the MCP Cheat Engine Server to safely analyze program memory through the Model Context Protocol. This read-only server lets you enumerate processes, read memory, scan for patterns, disassemble code, and analyze data structures, while keeping actions logged for auditing and safety.
You will connect to the MCP server from an MCP client and perform a sequence of actions to inspect memory without modifying it. Start by listing processes, attach to a target process you have permission to analyze, read memory regions to explore data, and use advanced tools to scan patterns, disassemble code, or analyze structures. Detach when your analysis is complete to keep the session clean.
Practical usage patterns include: start with a simple program such as a text editor, attach to that process, read memory regions to locate meaningful data, run a memory scan for a specific pattern, and then disassemble nearby code or analyze potential data structures. Always detach after you finish and review the security logs if something unexpected occurs.
Prepare your environment with Python and a suitable MCP client. Follow these steps to install and run the server locally.
Prerequisites you need to meet before installation:
Step-by-step commands you will run in order:
pip install -r requirements.txtpython server/main.py --testConfiguration and security details shape how you interact with memory and what you are allowed to access. The server runs in read-only mode by default to prevent memory modification and to protect system stability.
Security and safety notes emphasize using a whitelist of processes, enabling operation logging, and running with appropriate privileges on your platform. Always review the logs after your analysis.
Operational troubleshooting steps cover common issues like access errors, missing dependencies, unknown processes, and memory read failures. Use the provided test run to verify proper installation before performing deeper analysis.
Advanced usage examples show how to import compute tables and analyze Lua scripts, as well as how to inspect memory regions and resolve multi-level pointer chains to understand complex addresses.
For quick validation during setup, you can run the server in a debug mode to get verbose output and verify that memory reads and tool calls behave as expected.
Retrieve a list of currently running processes with basic details such as process name and PID.
Attach the MCP session to a specific process by providing the process ID.
Safely detach from the currently attached process to end memory operations.
Read a specified amount of memory from a given address and return the data in a chosen format.
Obtain the full virtual memory layout of the target process, including region protections and sizes.
Search memory for a specified byte pattern with optional start and end addresses and wildcards.
Disassemble a region of memory to view assembly instructions for analysis.
Inspect memory to identify and analyze potential data structures.
Follow multi-level pointers to resolve the final address.
Import existing Cheat Engine table files to guide memory queries.
Analyze Lua scripts in a safe mode to inspect scripts used by memory tools.