cheatengine-mcp-bridge MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

43 MCP tools for memory operations, code analysis, and debugging
Read/write integers, floats, strings, and follow pointer chains
Disassemble functions, identify C++ objects via RTTI, find cross-references
Hardware breakpoints and Ring -1 invisible tracing via DBVM
Auto-detect structures, field types, and generate AOB signatures

Démo en direct

Aperçu en pratique

cheatengine-mcp-bridge.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "cheatengine-mcp-bridge": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge"
      ]
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "cheatengine-mcp-bridge": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge"
      ]
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "cheatengine-mcp-bridge": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge"
      ]
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "cheatengine-mcp-bridge": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge"
      ]
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "cheatengine-mcp-bridge",
      "command": "TODO",
      "args": [
        "See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "cheatengine-mcp-bridge": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add cheatengine-mcp-bridge -- TODO 'See README: https://github.com/miscusi-peek/cheatengine-mcp-bridge'

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : cheatengine-mcp-bridge

How to solve a CTF memory analysis challenge with Cheat Engine MCP

👤 CTF participants working on binary exploitation or game hacking challenges ⏱ ~30 min intermediate

Quand l'utiliser : You have a CTF challenge that requires finding and manipulating values in a running process.

Prérequis

Windows with Cheat Engine installed — Download from cheatengine.org
MCP bridge running — pip install -r MCP_Server/requirements.txt

Déroulement

Scan for the target value

Attach to the CTF challenge process and scan for an integer value of 100 (my current score).✓ Copié

→ List of memory addresses containing the value 100
Narrow down the address

I changed the score to 95. Rescan to find which address actually holds the score.✓ Copié

→ Filtered list with likely candidate addresses
Trace the pointer chain

Find the pointer chain to this address so we can reliably locate it after restart.✓ Copié

→ Stable pointer path from base module

Résultat : A reliable pointer chain to the target value for the CTF solution.

Pièges

Value stored as float instead of integer — Try scanning as float or double if integer scan returns no results

Reverse engineer game data structures with AI assistance

👤 Game modders and reverse engineers analyzing proprietary software they own ⏱ ~45 min advanced

Quand l'utiliser : You want to understand the memory layout of a program's data structures for educational purposes.

Prérequis

Cheat Engine + MCP bridge running — pip install mcp pywin32
Target process you own or have authorization to analyze — Launch the application

Déroulement

Dissect the structure

Attach to the process and dissect the data structure at address 0x1A3F0000. Identify field types and sizes.✓ Copié

→ Structure layout with field offsets, types, and likely names
Find RTTI class info

Check if this address has RTTI information. What C++ class does it belong to?✓ Copié

→ Class name and inheritance chain from RTTI

Résultat : A documented data structure layout with field types and class hierarchy.

Pièges

RTTI stripped from release builds — Fall back to manual structure dissection and pattern analysis

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

cheatengine-mcp-bridge + filesystem

Export discovered structures and pointer maps to files for documentation

Document the data structures we found and save them as a markdown file in my notes folder.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
read_memory	address: str, size: int	Read raw bytes from a memory address
read_integer	address: str, size?: int	Read an integer value from memory
scan_all	value: str, type: str	Scan process memory for a specific value
aob_scan	pattern: str	Search for a byte pattern (array of bytes) in memory
disassemble	address: str, count?: int	Disassemble instructions at an address
dissect_structure	address: str, size?: int	Auto-detect structure layout at an address
get_rtti_classname	address: str	Get the C++ class name via RTTI for an object pointer
set_breakpoint	address: str, type?: str	Set a hardware breakpoint for debugging

Coût et limites

Coût d'exécution

Quota d'API: N/A — all local
Tokens par appel: 200–1000 tokens per tool call
Monétaire: Free — requires Cheat Engine (free) and Windows
Astuce: Use targeted scans (aob_scan, read_integer) instead of full memory dumps to reduce output size.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : N/A — local tool, no external credentials

Sortie de données : All operations are local via Named Pipes. No network calls.

⚠ This tool is designed for authorized security research, CTF competitions, and defensive analysis only. Do not use it against systems you don't own or have written authorization to test.
Windows only — requires Named Pipes support and Cheat Engine installed.
Memory manipulation can crash target processes. Save your work before attaching.

Dépannage

Erreurs courantes et correctifs

Named Pipe connection failed

Ensure Cheat Engine is running and the Lua bridge script is loaded. Check that both CE and the MCP server run with matching privilege levels (both admin or both user).

Vérifier : Check Cheat Engine's Lua console for pipe creation messages

Access denied reading memory

Run Cheat Engine as Administrator. Some processes require elevated privileges for memory access.

Vérifier : Right-click Cheat Engine → Run as Administrator

Scan returns no results

Try different value types (float vs int, 4-byte vs 8-byte). The value might be stored in an unexpected format.

Vérifier : Try a scan with 'All' value type

Alternatives

cheatengine-mcp-bridge vs autres

Alternative	Quand l'utiliser	Compromis
ida-pro-mcp	You need static binary analysis and disassembly rather than live memory manipulation	Static analysis only but much deeper code understanding
mcp-windbg	You need kernel-level debugging or crash dump analysis on Windows	More powerful debugging but steeper learning curve

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills