Practical overview
When it fits
Use it when Cheat Engine is part of a memory-analysis workflow and you want an MCP-compatible AI client to request inspection or reverse-engineering operations. Choose native named pipes for a Windows-local server or the documented TCP relay when the MCP server runs elsewhere.
Who it is for
- Researchers and developers using Cheat Engine who want to direct memory-analysis tasks through an MCP-compatible AI client.
- People building or investigating program and game memory workflows that involve pointer scans, structure inspection or reverse engineering.
Documented uses
- Read memory as integers, floats, strings or pointers.
- Follow pointer chains and inspect program structures.
- Identify C++ objects using RTTI and analyze or disassemble functions.
- Connect an MCP client to Cheat Engine using a local Windows named pipe or a TCP relay.
Requirements & limits
The repository is public and specifies an MIT license. The documented tool is self-hosted and requires a local setup with Cheat Engine, the bridge, a Python MCP server and an MCP client.
- The MCP server and Cheat Engine communicate through either a Windows named pipe or the documented TCP relay.
- The TCP relay allows the MCP server to run outside the Windows environment, but Cheat Engine and its Lua bridge remain on Windows.
- DBVM must be enabled only for workflows that use DBVM tools; the README warns that a Cheat Engine memory-region setting must be disabled.
- Shell-related tools require explicitly setting CE_MCP_ALLOW_SHELL=1, which the project flags as an arbitrary-code-execution risk.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect an MCP client through the Windows TCP relay
Configure a TCP path from an MCP client to Cheat Engine when the MCP server runs outside the Windows environment hosting Cheat Engine.
Before you start
- Cheat Engine and the Lua bridge running on Windows
- Python and the project repository
- An MCP client that can use environment variables in its server configuration
Steps
Load MCP_Server/ce_mcp_bridge.lua in Cheat Engine.
Start ce_tcp_relay.py on Windows with the documented host and port arguments.
In the MCP server environment, install dependencies from MCP_Server/requirements-tcp.txt.
Run or configure mcp_cheatengine.py with CE_MCP_TRANSPORT=tcp, CE_MCP_HOST and CE_MCP_PORT set to match the relay.
Expected outcome
The MCP server is configured to reach the Windows-hosted bridge through the TCP relay.
Guide limitations
- Cheat Engine and the Lua bridge still run on Windows.
- The relay should be bound only to trusted interfaces because reachable clients can control the bridge.
Set up the native Windows named-pipe connection
Load the bridge in Cheat Engine and configure an MCP client to launch the Python server locally.
Before you start
- Windows
- Cheat Engine
- Python
- An MCP client with server configuration
Steps
Install the project requirements from MCP_Server/requirements.txt, or install mcp and pywin32.
Load MCP_Server/ce_mcp_bridge.lua using Cheat Engine's Lua Engine or script executor.
Add the documented Python server command and script path to the MCP client configuration, then restart the client.
Use the MCP ping tool to check the connection.
Expected outcome
The MCP client is configured to connect to the Cheat Engine bridge over the native named pipe.
Guide limitations
- Native named-pipe mode is Windows-only.
- The README warns to disable Cheat Engine's “Query memory region routines” setting.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- miscusi-peek/cheatengine-mcp-bridge · Official homepage title · retained in its source language