ce-mcp
Related Servers
Alternatives to ce-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI to directly control Cheat Engine for process attachment, memory scanning, reading/writing, address list management, speed hack, Lua/Auto Assembler execution, and CT file management via the MCP protocol.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Cheat Engine for memory reading/writing, scanning, debugging, and .NET/Mono game reverse engineering through 43 Chinese-language MCP tools, with thread-safe named-pipe communication.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Cheat Engine 7.6 that enables AI agents to perform memory scanning, reading/writing, process manipulation, debugging, and code injection via a Lua named pipe bridge.3GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform low-level Windows process memory research, including process attachment, memory scanning, reading/writing, pointer chasing, remote code execution, and inline hooking via MCP tools and Lua scripting.2MIT
- AlicenseAqualityFmaintenanceProvides Cheat Engine-like capabilities for game hacking and reverse engineering through Frida, enabling memory scanning, value modification, pattern matching, function hooking, and code injection across processes.4274MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to analyze binaries, debug processes, and inspect kernel state using Ghidra, x64dbg, WinDbg, and ILSpyCmd.9Apache 2.0
TDQS
Scored across 42 tools
Most tools have clearly distinct purposes, even within groups like scanning or table management. A few pairs (e.g., find_what_accesses vs find_what_writes) could be confused, but descriptions clarify the differences. Overall, the tool surface is well-organized.
Tools use snake_case consistently, but the order of verb and noun varies: some are verb_noun (e.g., memory_read), others noun_verb (e.g., table_add). The ce_* prefix and occasional verb-first names (e.g., breakpoint, disassemble) break the pattern, making it somewhat predictable but not perfectly consistent.
42 tools is high for a single-purpose server, exceeding the 'heavy' threshold of 25+. While each tool serves a specific Cheat Engine function, the sheer number may overwhelm agents and increase selection errors. A more compact set could cover the same functionality.
The tool set covers the core Cheat Engine workflows: process management, memory scanning/reading/writing, pointer handling, code injection, table management, and Mono support. Minor gaps exist (e.g., no generic 'find what reads'), but the surface is comprehensive for game hacking automation.