Provides tools for inspecting Mono/IL2CPP (Unity) games at runtime: initializing the Mono runtime, listing assemblies, classes, fields and methods, reading field values, reading statics, dumping the game's class structure, and searching for live object instances in memory.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@asymptomatik-cheatengine find my health in the tutorial, it's 100 and drops when I'm hit"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Drive Cheat Engine from Claude Code: attach to a game, scan for values, read and write memory, follow pointers, watch what code touches an address, patch code, inspect Mono / IL2CPP (Unity) objects, take screenshots — by asking Claude in plain language.
You: find my health in the tutorial, it's 100 and drops when I click "Hit me"
Claude: [unknown scan] → [decreased] → [between 1 and 99] → 0x015887E0 = 85
[watchpoint] → written by "sub [rbx+00000800],edx" at Tutorial-x86_64.exe+47F6D
[pointer scan] → ["Tutorial-x86_64.exe"+346C10]+800 (static, survives restarts)Everything runs on your machine: the plugin talks to Cheat Engine through a local named pipe; nothing is sent anywhere else.
Use it on games and programs you own, single-player or offline. Online games' terms of service usually forbid memory editing, and anti-cheat systems can ban you.
Windows
Cheat Engine 7.7 or later (the plugin refuses older versions: it relies on 7.7's scan API)
Node.js 22.13 or later on your PATH (node --version)
Claude Code
Related MCP server: ce-mcp
In Claude Code:
/plugin marketplace add djethino/asymptomatik-claude-plugins
/plugin install asymptomatik-cheatengine@asymptomatikRestart Claude Code.
Install the Cheat Engine side, once:
/ce-installIt finds Cheat Engine (registry or Program Files) and writes a small loader into its autorun folder. A Windows administrator prompt appears if that folder is not writable.
Restart Cheat Engine. Its main window now has an MCP menu and a status label.
Ask Claude to check: "ce_status" — it should say Connected: Lua 5.3 - CE 7.7 ... and loader installed.
Updates of the plugin reach Cheat Engine by themselves: the loader runs a per-user copy of the CE script (%LOCALAPPDATA%\cheatengine-mcp\) that the plugin refreshes at every start. /ce-install is only needed again if ce_status reports the loader as missing or outdated.
Two independent locks:
What it locks | Default | Change it | |
SAFE mode | The tools that can crash the game or Cheat Engine: | On at every start |
|
Read-only option | Everything that changes the game or writes a file (memory writes, freezes, hotkeys, patches, table saves...) | Off |
|
Reading, scanning, writing values and freezing are what Cheat Engine is for: they stay available in SAFE mode.
Every tool parameter reaches Cheat Engine's Lua as data, never as code, so no input — a process name with a quote, a string read from the game — can run commands of its own.
Area | Tools |
Connection |
|
Processes and memory |
|
Value scans |
|
Pointers |
|
Address list (cheat table) |
|
Code and debugging |
|
Mono / IL2CPP (Unity) |
|
Screen |
|
Long operations |
|
Setup |
|
Some details worth knowing:
Long operations do not freeze Cheat Engine. Scans, pointer scans and instance searches run in the background with a progress window (with a Cancel button) in CE, and send progress notifications to Claude Code. Pass wait=false to get a job id at once and check it later.
Scans are Claude's own: they never touch the scan you run by hand in CE's main window. Several named scans can run side by side (scan_name).
Code changes go through the address list: ce_asm_inject, ce_asm_script and ce_code_entry create auto assembler entries you can see and toggle in CE; disabling one restores the original code.
Screenshots stay off the disk by default: the image goes straight to Claude. Give save_path to keep the PNG. The game window must not be minimized.
Lists are paginated (offset, limit, filter), and long outputs end with a line telling Claude how to read the rest.
Not connected: Cannot connect to \\.\pipe\ce-mcp — Cheat Engine is not running, or its MCP plugin is not loaded. Check ce_status (loader state), run /ce-install if needed, restart CE, and check that CE's MCP menu shows the server as started.
Cheat Engine 7.7 or later is required — update Cheat Engine.
Cheat Engine did not answer within ... s — a dialog is probably open in Cheat Engine (an error, a confirmation): close it. The next call reconnects by itself.
Another Claude Code session is using Cheat Engine — two Claude Code sessions cannot drive the same Cheat Engine at once (their calls would mix). The message tells Claude how to take it over if you want this session to.
Overlays do not show — CE's D3D hook only supports DirectX 9, 10 and 11, and does not work with every game. The overlay tool warns when the hook has not seen any frame of the game.
Mono tools fail — run ce_mono_init first (it can take a minute); Mono tools only apply to .NET / Unity games.
The MCP server (dist/index.js, Node.js, no runtime dependency) connects to the Lua server Cheat Engine opens on a named pipe (openLuaServer, started by the CE-side plugin). Each tool call becomes one Lua chunk that also applies the SAFE gate, so the check cannot be skipped; results come back through CE's pipe protocol. Calls are serialized: Cheat Engine runs every pipe script on its single Lua state.
Development: npm run build (type check + bundle; dist/ is committed because Claude Code does not build plugins), npm test (offline, against a fake Cheat Engine that runs the generated Lua in a real Lua interpreter).
MIT — Copyright (c) 2025 ASymptOmatik
This server cannot be deployed
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Securely control computers you explicitly pair through files, terminals, processes, screenshots, desktop UI/input, clipboard, browser automation, diagnostics, and document tools.
Safe folder access for ChatGPT and Claude: read, write and search files, risky tools opt-in.
