cheat-engine -python

This MCP server exposes Cheat Engine style memory analysis and debugging capabilities through a read-only MCP interface. It allows you to list accessible processes, attach to a target process, read memory regions with multiple data types, perform pattern scans, disassemble code, and analyze memory structures. The server is designed for safety and auditing, operating in read-only mode with operation logging enabled. To use it, configure your MCP client (such as Claude Desktop) to connect to the cheat-engine MCP server and issue tools like list_processes, attach_to_process, read_memory_region, scan_memory, disassemble_code, and analyze_structure. The tools return structured results that help you inspect memory without modifying it. Ensure the target process is whitelisted before attaching, and detach when finished to maintain security and stability.

Prerequisites:

• Supported OS: Windows 10/11 (primary); Linux/macOS in limited capacity
• Python 3.9+ installed
• Administrator/root access for memory access

Step-by-step:

1. Acquire the server sources (clone or download the cheat-engine-server-python repo).
2. Install Python dependencies:

   pip install -r requirements.txt
   

3. Run a quick test to ensure the server starts:

   python server/main.py --test
   

   You should see a message indicating the MCP Cheat Engine Server initialized successfully.
4. If used with Claude Desktop or another MCP client, configure the client with the MCP server entry (see Quick Start).
5. Start normal operation:

   python server/main.py
   

6. When finished, stop the server and monitor logs if needed for auditing.

Notes and tips:

• The server runs in read-only mode by default to prevent memory writes. This is ideal for safety and auditing.
• Ensure the target processes are whitelisted in server/config/whitelist.json to attach successfully.
• Review server/settings.json to adjust read limits, logging verbosity, and performance parameters like max_memory_read and scan_timeout.
• Logs are typically written to logs/operations.log for auditing purposes.
• If you encounter attachment failures, verify whitelist settings and that the process is not protected by the operating system's protections.
• When testing pattern scans, use patterns with wildcards represented as ?? for unknown bytes.
• For Claude Desktop users, the MCP config snippet in the Quick Start section should be adapted to the local paths of your cheat-engine server installation.