Opal Emu MCP
Related Servers
Alternatives to Opal Emu MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA 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.1334MIT
- AlicenseAqualityBmaintenanceAn 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.896 PyPI26MIT
- 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.19 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.17 npm54MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: listing, loading, resetting, capturing, controlling, and advancing frames. There is no overlap or ambiguity between any pair of tools.
All tool names follow the verb_noun pattern (list_roms, load_rom, reset_emulator, get_current_screen, control_emulator, skip_frames). The style is completely consistent across the set.
6 tools is well-scoped for an emulator MCP server, providing the essential operations without bloat. The count aligns with the domain's core workflow.
The core emulator loop is covered: loading ROMs, controlling input, advancing frames, resetting, and capturing screens. However, save/load state functionality is absent, which is a common and useful feature for emulator workflows, though not strictly required for basic operation.