A
licenseA
qualityD
maintenanceA Model Context Protocol server that enables LLMs to interact with a GameBoy emulator, providing tools for controlling the GameBoy, loading ROMs, and retrieving screen frames.
13
36
MIT
Opal Emu MCP
by thevalmarch
Related Servers
Alternatives to Opal Emu MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server for the Pyxel retro game engine that enables AI models to autonomously run, verify, and iterate on retro game programs. It includes tools for visual verification through screenshots, sprite and layout analysis, and audio rendering.829MIT
- AlicenseNot gradedqualityBmaintenanceA headless MCP server that lets an LLM load Game Boy Advance ROMs, step through instructions, read and write memory, and manage breakpoints, watchpoints, and registers.22 npmMozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows LLMs to interact with Game Boy games through PyBoy emulation, providing capabilities to load ROMs, control games, capture screens, save/load states, and maintain game knowledge.1MIT
- FlicenseAqualityCmaintenanceAn MCP server adapter that allows LLM agents to autonomously play World of ClaudeCraft by wrapping the game's headless environment as MCP tools for state reading and action execution.7-
- AlicenseDqualityDmaintenanceAn MCP server that enables LLMs to 'see' what's happening in browser-based games and applications through vectorized canvas visualization and debug information.16 npm54MIT
TDQS
A4.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: listing ROMs, loading, resetting, capturing the current screen, sending controller input, and advancing frames. The three tools that return screenshots (get_current_screen, control_emulator, skip_frames) are differentiated by whether they advance the game, and the descriptions make these boundaries explicit.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern: list_roms, load_rom, reset_emulator, get_current_screen, control_emulator, skip_frames. There are no mixed conventions or vague standalone verbs.
Tool Count5/5
Six tools is well-scoped for an emulator control server. Each tool earns its place, covering discovery, loading, reset, screen capture, input, and frame advancement without redundancy.
Completeness3/5
The core emulation loop is covered, but save/load state operations are absent, meaning agents cannot preserve progress before risky actions or reset. An explicit stop/unload tool and system selection for problematic disc images are also missing, creating notable gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues