No user-submitted related servers found.
Scored across 37 tools
The tool set has several clusters that a naive agent could confuse (read_memory / query / state_observer / frame_snapshot / watch_value for state reads; step / batch_step for stepping; watch_value / breakpoint(trace) / state_observer for observing), but nearly every description carries an explicit ROUTING block that names the intended tool for each case, which sharply reduces misselection. Boundaries remain slightly blurred by design given the mega-tools (breakpoint, query, scan, replay) that fold many actions into one.
Every tool uses the identical ppsspp_ snake_case prefix and mostly a verb_noun shape (read_memory, write_register, press_button, hold_buttons, batch_step), with a few noun-named aggregators (context, health, session, replay). The convention is uniform and predictable throughout.
37 tools is on the heavy side for a single MCP server and several obvious groupings (batch_step/batch_status/batch_cancel, list_scripts/run_script/reload_scripts) could plausibly be folded together. The domain genuinely spans sessions, memory, breakpoints, GPU, input, replay, and scripting, so the breadth is partly earned, but it sits at the upper edge of comfortable.
The surface covers the full debugging lifecycle end to end: session start/stop/wait, memory read/write/scan/diff, disassembly and search, breakpoints and value watches, register/PC evaluation, GPU stats/dump/record, screenshots, input, replay, batching, and script management. There are no obvious dead ends for the stated PPSSPP-debugging purpose.