PCSX2 MCP
Related Servers
Alternatives to PCSX2 MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for PCSX2 and other emulators that speak the PINE protocol. Read and write 8/16/32/64-bit emulator memory and control save states for PlayStation-family emulation.1415 npm2MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for debugging Windows processes using WinDbg and CDB. It enables users to attach to processes, manage breakpoints, inspect memory, and control execution flow through natural language.2-
- AlicenseNot gradedqualityDmaintenanceMCP server for the mGBA Game Boy/GBA emulator, enabling full emulator control, memory access, debugging, and screenshot capture through natural language.4MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for Windows process memory inspection/editing and crash dump analysis, enabling live memory scanning, patching, pointer resolution, disassembly, and offline dump examination via structured tool calls.MIT
- AlicenseBqualityDmaintenanceAn MCP server providing direct access to gdb-multiarch for debugging Nintendo Switch executables on Yuzu or hardware via a GDB stub. It features specialized tools for offset-based breakpoints, instruction patching, and frame-pointer backtraces relative to the game's base address.333MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for remote debugging with gdbserver, offering full debugging capabilities including breakpoint control, stepping, memory inspection, and process management.29 PyPIMIT
TDQS
Scored across 40 tools
There is noticeable overlap between breakpoint and watchpoint tools, with two sets (regular and debug) that could confuse. Tools like set_breakpoint and set_watchpoint have similar purposes, and distinctions are not always clear. Most other tools are well-separated.
Most tools follow a verb_noun pattern with underscores (e.g., read_memory, set_breakpoint). However, a few tools use standalone nouns (status) or noun_verb (memory_diff), and verbs vary (get vs read, set vs write). Overall consistent but with minor deviations.
With 40 tools, the surface is quite large. While the PCSX2 domain is complex, several groups (e.g., 9 breakpoint tools, 9 memory tools) could potentially be consolidated. The count is on the high side but still manageable for a full-featured debugger server.
The tools cover connection, control, savestates, registers, disassembly, memory, breakpoints, tracing, and rewind, which is comprehensive. However, a tool to list active non-debug breakpoints is missing, and there is no way to query emulation state (paused/running). Minor gaps but overall solid.