Skip to main content
Glama
AstralVoidZ

ppsspp-dfx

by AstralVoidZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ppsspp-dfx

No user-submitted related servers found.

    Related Servers

    • mcp-ppsspp

      dmang-dev
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that exposes PPSSPP — the PlayStation Portable emulator — to any MCP-compatible client (Claude Desktop, Claude Code, etc.) via PPSSPP's built-in WebSocket debugger interface. Read and write PSP memory, drive games with button input, capture screenshots, set CPU breakpoints, inspect MIPS Allegrex registers — all through a clean tool interface. No bridge plugin needed; PPSSPP's debugg
      23
      19 npm
      8
      MIT

    • ce-mcp

      IMRX44
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to programmatically control Cheat Engine for memory scanning, editing, cheat table management, and reverse engineering tasks.
      42
      MIT

    • GDB MCP Server

      yywz1999
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with GDB for debugging via the MCP protocol. Supports setting breakpoints, stepping through code, inspecting memory and registers, and more.
      86
      MIT

    • GDB MCP Server

      zjm1060
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to debug embedded systems by providing a comprehensive interface for GDB operations across multiple architectures like ARM and x86. It supports remote debugging via gdbserver or QEMU, allowing for detailed inspection of memory, registers, stack frames, and variables.
      31
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 41 tools

    Disambiguation3/5

    Most tools have clear targets (memory, CPU, input, GPU), but several clusters overlap: ppsspp_query is a catch-all that competes with get_pc/frame_snapshot/state_observer, and breakpoint/wait_breakpoint/trace_memory_access plus step/batch_step have adjacent behaviors. The detailed usage text resolves most ambiguity, so an agent can pick correctly if it reads closely.

    Naming Consistency3/5

    All tools share the ppsspp_ snake_case prefix, which helps, but the internal convention varies: many are verb_noun (read_memory, press_button, dump_texture), while others are generic nouns or action-dispatch names (session, breakpoint, query, replay, step), and some are inverted (batch_cancel, memory_info_search). Still readable and predictable enough.

    Tool Count2/5

    41 tools is a large surface for agents to discover and keep straight, even though the server covers many subdomains (session, memory, CPU, input, GPU, replay, scripts, batch). Many tools could be consolidated further, and the count sits well above the 25-tool comfort threshold.

    Completeness5/5

    For a PPSSPP debugging/automation server, the surface is remarkably thorough: session lifecycle, memory read/write/scan/assemble, CPU stepping/breakpoints/tracing, input control, GPU capture, replay, batch jobs, scripts, and log analysis are all present. I don't see an obvious critical workflow dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources