A
licenseNot graded
qualityD
maintenanceEnables debugging of PlayStation games through DuckStation by providing MCP tools for execution control, register access, memory inspection, breakpoints, process management, and log analysis.
MIT
mame-mcp
by astrobleem
Related Servers
Alternatives to mame-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to reverse engineer Nintendo 64 ROMs and PlayStation 2 ELF binaries through MIPS disassembly, binary and metadata inspection, memory and crash analysis, and repository reference tracing with structured, verifiable evidence.768 npm7MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to control an MSX emulator for debugging and reverse-engineering, including memory and code inspection, execution control, and saving annotations via MCP.-
- AlicenseNot gradedqualityCmaintenanceEnables agents and scripts to inspect, disassemble, emulate, debug, patch, and mod SNES ROMs, including Super Mario World-specific level and route tooling, through callable tools backed by a Rust core.MIT
- FlicenseAqualityDmaintenanceEnables programmatic control of the mGBA emulator for Game Boy, Game Boy Color, and Game Boy Advance games, including screenshot capture, memory reading, sprite data dumping, and custom Lua script execution for automated testing and game analysis.66-
- AlicenseAqualityDmaintenanceEnables autonomous debugging of Commodore 64 programs through the VICE emulator with semantic interpretation of C64-specific data structures, memory layouts, VIC-II states, and PETSCII encoding for AI-assisted 6502 assembly debugging.261MIT
TDQS
C2.8/5.0
Scored across 25 tools
Disambiguation2/5
Multiple tools have overlapping purposes: three different Lua execution tools (mame_exec_lua_live, run_lua_script, run_lua_inline), two tracing tools (trace_memory_access, trace_cchip_superman), and two gameplay automation tools (mame_drive_to_gameplay, mame_capture_game_tick) that are easy to confuse. Descriptions help distinguish them, but an agent would likely struggle to pick the right one without deep domain knowledge.
Naming Consistency2/5
Tool names are mixed: some use the mame_ prefix (mame_launch, mame_get_regs), while others do not (ping, audit_romset, trace_memory_access). Verb patterns also vary (run_lua_script vs mame_exec_lua_live, capture_leaf_io vs mame_capture_game_tick). While all use snake_case, the inconsistent prefix and verb choices make the set feel disjointed.
Tool Count3/5
25 tools is at the high end of the acceptable range and feels heavy for the server's purpose. Many tools could be consolidated (e.g., Lua execution variants, tracing helpers), which would reduce the surface area without losing functionality. Still, the complexity of MAME emulation and debugging justifies a larger toolset than typical servers.
Completeness4/5
The server covers a broad range of MAME operations: session lifecycle, memory/register access, input injection, Lua scripting, state save/load, tracing, and gameplay capture. Minor gaps exist, such as no tool to list save states or enumerate devices, but these are workable. The core workflows for reverse engineering and deterministic gameplay are well supported.
Maintenance
ActivityStale
ResponsivenessNo recent community issues