cheatengine-mcp-bridge MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

cheatengine-mcp-bridge.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren 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"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: 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

Wann einsetzen: You have a CTF challenge that requires finding and manipulating values in a running process.

Voraussetzungen

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

Ablauf

Scan for the target value

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

→ 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.✓ Kopiert

→ 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.✓ Kopiert

→ Stable pointer path from base module

Ergebnis: A reliable pointer chain to the target value for the CTF solution.

Fallstricke

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

Wann einsetzen: You want to understand the memory layout of a program's data structures for educational purposes.

Voraussetzungen

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

Ablauf

Dissect the structure

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

→ 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?✓ Kopiert

→ Class name and inheritance chain from RTTI

Ergebnis: A documented data structure layout with field types and class hierarchy.

Fallstricke

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: N/A — all local
Tokens pro Aufruf: 200–1000 tokens per tool call
Kosten in €: Free — requires Cheat Engine (free) and Windows
Tipp: Use targeted scans (aob_scan, read_integer) instead of full memory dumps to reduce output size.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: N/A — local tool, no external credentials

Datenabfluss: 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.

Fehlerbehebung

Häufige Fehler und Lösungen

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).

Prüfen: 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.

Prüfen: 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.

Prüfen: Try a scan with 'All' value type

Alternativen

cheatengine-mcp-bridge vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen