How do I connect Cheatengine MCP Bridge MCP Server to Claude?

The listing records `pip install -r MCP_Server/requirements.txt` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Code, Cursor as compatible clients.

Is Cheatengine MCP Bridge MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Cheatengine MCP Bridge MCP Server do?

Cheatengine MCP Bridge MCP Server documents 16 tools to the agent, including assemble_instruction, compile_c_code, create_process. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Cheatengine MCP Bridge

Unclaimed

by miscusi-peek

Connect your favorite AI agents directly to Cheat Engine via MCP. Automate reverse engineering, pointer scanning, and memory analysis using natural language.

Install

$pip install -r MCP_Server/requirements.txt

Set up this server

Compare servers My Stack

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions

ai-agentsai-toolsautomationcheat-enginectf-toolsdebuggerdebugginggame-researchgame-securityluamcpmcp-clientmcp-servermemory-analysismodding-toolspentestingpythonreverse-engineeringvibecheatingvibehacking

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

16 of 16 tools

Documented tools (16)

From project documentation. A server handshake does not verify each tool’s description or behavior.

assemble_instruction

Assemble a single x86/x64 instruction to bytes

compile_c_code

Compile C source into injected shellcode

create_process

Launch a new process under CE's control

dbk_get_cr3

Read the CR3 register for the target process

dissect_structure

Auto-detect fields and types

enable_windows_symbols

Enable PDB symbol resolution

find_window

Locate a window by title or class

generate_api_hook_script

Generate a CE auto-assembler API hook template

get_address_list

Enumerate entries in the active cheat table

get_pixel

Sample a pixel color at screen coordinates

get_rtti_classname

Identify C++ object types

inject_dll

Load a DLL into the target process

read_pointer_chain

Follow [[base+0x10]+0x20] paths

read_process_memory_cr3

Read physical memory via CR3 bypass

send_window_message

Post WM messages to a target window

start_dbvm_watch

Ring -1 invisible tracing

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Cheatengine MCP Bridge MCP Server

How do I connect Cheatengine MCP Bridge MCP Server to Claude?: The listing records `pip install -r MCP_Server/requirements.txt` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Code, Cursor as compatible clients.
Is Cheatengine MCP Bridge MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Cheatengine MCP Bridge MCP Server do?: Cheatengine MCP Bridge MCP Server documents 16 tools to the agent, including assemble_instruction, compile_c_code, create_process. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.