PlugWiki
cheatengine-mcp-bridge logo

Cheat Engine MCP Bridge: Setup for Claude, Cursor and Other Apps

CommunityLocal

Lets an AI assistant inspect and change the memory of another program through Cheat Engine on Windows.

Cheat Engine is a tool for examining and editing the memory of running programs. It is used for game modding, trainers, reverse engineering and security research. This bridge gives an assistant about 175 tools to read values, scan for patterns, disassemble code, set breakpoints and write to memory.

It runs on your Windows PC and needs Cheat Engine open with the bridge script loaded. It can modify other programs, run arbitrary code and delete files, so use it only on software you own or are allowed to test.

Good for

  • Reverse engineers and security researchers analyzing a program's memory
  • Modders and trainer authors who want help finding addresses and patterns
  • CTF players working through binary challenges

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install cheatengine-mcp-bridge

Claude Code

  1. 1

    Copy this prompt.

    Add the cheatengine-mcp-bridge server to Claude Code. Run this command:
    
    claude mcp add cheatengine -- python C:/path/to/cheatengine-mcp-bridge/MCP_Server/mcp_cheatengine.py
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Windows, Python 3.10+, Cheat Engine with the bridge script.

Read-only mode: There is no read-only mode. Shell tools stay off unless CE_MCP_ALLOW_SHELL=1 is set.

Clone the repository and run pip install -r MCP_Server/requirements.txt. In Cheat Engine, open File, Execute Script and run MCP_Server/ce_mcp_bridge.lua until it prints that the MCP server is listening. Then replace the example path with where you cloned the repo. The README shows the same command in a generic config and a Codex TOML block; the configs here are adapted from it and are generated. To use the TCP relay from WSL or another machine, see the README.

Built from the package data we hold. Not yet tested by us.

Tools

  • Checks the bridge is connected

    Replies with the bridge version so you know the assistant can reach Cheat Engine.

    Try: “Ping Cheat Engine.”

    Read · ping

  • Lists running processes

    Returns the processes on the machine with their IDs and names.

    Try: “Which processes are running?”

    Read · get_process_list

  • Attaches Cheat Engine to a process

    Opens a process by ID or name so later reads and writes target it.

    Try: “Attach to notepad.exe.”

    Write · open_process

  • Shows the attached process

    Returns its ID, name, module count and architecture.

    Try: “What process is attached?”

    Read · get_process_info

  • Lists the process's loaded modules

    Lists DLLs and modules with base addresses and sizes, in pages.

    Try: “List the modules of the attached process.”

    Read · enum_modules

  • Reads raw bytes from memory

    Returns the bytes at an address in the attached process.

    Try: “Read 16 bytes at the base address.”

    Read · read_memory

  • Reads a number from memory

    Reads a byte, word, dword, qword, float or double at an address.

    Try: “Read the dword at the player address.”

    Read · read_integer

  • Reads text from memory

    Reads a string, narrow or wide, up to a length you set.

    Try: “Read the string at that address.”

    Read · read_string

  • Follows a pointer chain

    Follows a multi-level pointer chain and reports every step.

    Try: “Resolve [[base+0x10]+0x20]+0x8.”

    Read · read_pointer_chain

  • Starts a memory value scan

    Runs a first scan for a value of a chosen type, or an unknown-value scan.

    Try: “Scan for the value 100.”

    Read · scan_all

  • Narrows a scan

    Filters the earlier scan results, for example to values that increased.

    Try: “Now keep values that decreased.”

    Read · next_scan

  • Searches memory for a byte pattern

    Finds an array-of-bytes pattern such as 48 89 5C 24.

    Try: “Find the pattern 48 89 5C 24.”

    Read · aob_scan

Read from the source code

Permissions

high risk · 7 things to watch

High risk

The assistant can change and run code in other programs, execute any Lua, and delete files on your PC. Our advice is to use it only on software you own, in a virtual machine or test PC, with approval on for every call.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It changes and runs code in other programs

    Tools such as write_memory, auto_assemble, inject_dll and execute_code alter or run code inside the attached program. Use it only on software you own or have permission to test. github.com

  • evaluate_lua runs any Lua code

    evaluate_lua, create_thread and queue_to_main_thread execute arbitrary Lua inside Cheat Engine, with no read-only switch. Do not connect an assistant you do not trust. github.com

  • It can permanently delete files

    delete_file removes a file on the Cheat Engine host for good. Keep approval on for each tool call. github.com

  • Shell tools are off unless you switch them on

    run_command and shell_execute are refused unless CE_MCP_ALLOW_SHELL=1 is set at server start. Leave it unset unless you need them. github.com

  • Kernel and hypervisor tools can crash Windows

    The README says some kernel-mode settings cause CLOCK_WATCHDOG_TIMEOUT blue screens when they conflict with DBVM or anti-cheat. Save your work before using DBVM or DBK tools. github.com

  • The optional TCP relay gives control to anyone who reaches it

    The README warns that anyone who can reach the relay can control the bridge. It binds to 127.0.0.1 by default, so keep it there. github.com

  • Windows only for the default setup

    The default pipe mode uses a Windows named pipe via pywin32. The TCP relay lets the MCP server run elsewhere while Cheat Engine stays on Windows. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyNo read-only mode is documented. The reading tools only read, but the write, code-execution and file tools are always registered.
Talks toOptional local TCP relay (127.0.0.1:9876 by default)
Sign-in and keysNo credentials. Access depends on who can reach the named pipe or the optional TCP relay.
Scopes
  • Cheat Engine process access

  • Optional DBK kernel driver and DBVM hypervisor

Questions

Is it official?

No. It is a community project by miscusi-peek and is not made by the Cheat Engine team.

What do I need before I install it?

Windows, Python 3.10 or later, and Cheat Engine with MCP_Server/ce_mcp_bridge.lua loaded. Install the Python packages from the requirements file, then add the server to your client.

Does it work on Mac or Linux?

Not directly. Cheat Engine and the bridge run on Windows. The optional TCP relay lets the MCP server run on another machine, a VM or WSL.

Can it run shell commands?

Only if you set CE_MCP_ALLOW_SHELL=1 when the server starts. Without it the shell tools return an error.

Is it safe to use with online games?

Our advice is not to. The README says its kernel-mode features can conflict with anti-cheat, and its author states the project is for education and research and that he does not condone cheating in multiplayer games or violating Terms of Service. Changing another program's memory may also break a game's rules or the law.

Can I run it read-only?

No. The README documents no read-only mode, and the write, script and file tools are always registered.

How many tools does it have?

The source registers about 175 tools, and this page lists a selection, so the list here is partial.

Which clients does it work in?

The README shows a generic MCP config and a Codex TOML block, and names Claude, Cursor and Copilot as clients. It runs locally over stdio.

Information

updated Nov 2, 2026

Publisher
Community
Transport
stdio
Auth
None
License
MIT
Last commit
Aug 14, 2026
Open issues
2

GitHubIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. Cheat Engine MCP Bridge README · github.com
  2. mcp_cheatengine.py (tool registrations) · github.com
  3. ce_tcp_relay.py · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.