MCP Server

CheatSpecter includes an MCP server, so an AI assistant such as Claude can work on a game with you: "find my money and make it 9999", "what code lowers my health?", "save that as a cheat".

It runs on your computer and talks to the CheatSpecter payload on the PS5. Nothing extra is installed on the console.

What you need

• The CheatSpecter payload running on the PS5 (see Installation), with ps5debug-NG.
• A computer on the same network.
• The Claude desktop app, or any other MCP client that can run a local (stdio) server.

Install in the Claude desktop app

1. Download cheatspecter-<version>.mcpb from the Releases page.
2. Open the file. Claude shows an install prompt.
3. Enter the PS5's address when asked (the one shown in the notification when the payload starts, for example 192.168.1.50). You can leave it empty and tell Claude the address later.

Then ask Claude something like "What is running on my PS5?". It calls console_status first.

Because the PS5's address can change between restarts, you can always say "my PS5 is at 192.168.1.60 now" and Claude will switch.

Other MCP clients

Build the server (see Building from Source) and point your client at it:

{
  "mcpServers": {
    "cheatspecter": {
      "command": "node",
      "args": ["/path/to/cheatspecter/mcp/build/server/index.mjs"],
      "env": { "CHEATSPECTER_HOST": "192.168.1.50" }
    }
  }
}

Setting	Meaning	Default
CHEATSPECTER_HOST	The PS5's address	none; set it with console_status
CHEATSPECTER_PORT	The payload's port	8744

It speaks MCP over standard input and output and needs Node.js 18 or newer.

How a session usually goes

1. console_status: is the console there, and which game is running?
2. scan_start with the value you can see, then you change it in the game, then scan_next, until few matches remain.
3. write_memory to prove which one it is.
4. watch while you make the value change, to find the code that writes it.
5. disassemble and find_pattern to turn that into something lasting.
6. add_cheat, then set_cheat to try it.

Cheats the assistant saves go into the same .cspector file on the PS5 that the web app loads, so they appear there as switches.

Good to know

• You still play the game. The assistant cannot press buttons on the controller. It will ask you to fire a shot or spend some money and tell it the new number.
• Searches take time. A first search of a big game can take over a minute. If a tool answers "still running", the assistant calls scan_status.
• Addresses are shown and accepted as a module and an offset (game+0x1A2B, libSomething.prx+0x40), which stay right when the game restarts.
• One debugging session. watch cannot run while the web app is tracing or paused in the debugger, and the other way round.
• Starting a game closes the one that is running. launch_game tells the assistant to check with you first.
• Writes are real. write_memory and set_cheat change the running game. Save first.

The server and its original 16 tools were tried by hand against a real PS5 in 0.3.0. The nine added in 0.4.0 (addresses, references, engine names, structures, text search, kept cheats) have only been tested against the simulated console.

The full list is in the MCP Tool Reference.