MCP-openMSX
@nataliapc
A Model Context Protocol (MCP) server for automating openMSX emulator instances. This server provides comprehensive tools for MSX software development, testing, and automation through standardized MCP protocols.
Overview
What is MCP-openMSX?
MCP-openMSX is a Model Context Protocol server for automating openMSX emulator instances. It provides comprehensive tools for MSX software development, testing, and automation, bridging AI-assisted development (e.g., GitHub Copilot, Claude Desktop) with retro computing (MSX systems).
How to use MCP-openMSX?
Install the precompiled NPM package via npx @nataliapc/mcp-openmsx. Configure it in your MCP client (VSCode or Claude Desktop) using JSON with STDIO or HTTP transport. Environment variables allow customizing paths to the openMSX executable, share directory, screenshot folder, and more.
Key features of MCP-openMSX
- Emulator control: launch, close, power, reset, speed, machine/extension list
- Media management: insert/eject ROM cartridges, floppy disks, and cassette tapes
- BASIC programming support with tools to edit and run programs
- Full CPU debugging with breakpoints, memory inspection, and step execution
- Video control: VDP register manipulation and screen capture
- Memory operations: read/write RAM, VRAM, and I/O ports
- Hybrid documentation search (semantic embeddings + BM25) offline
Use cases of MCP-openMSX
- Automated testing of MSX software using AI-driven emulator control
- Debugging MSX programs with breakpoints, memory inspection, and step execution
- Developing and running BASIC programs directly from an AI assistant
- Managing media (ROM, disk, tape) for retro gaming or development
- Capturing screenshots and screen dumps for documentation or analysis
FAQ from MCP-openMSX
Does MCP-openMSX require openMSX to be installed?
Yes. The server controls a local openMSX emulator instance. You can specify the executable path via the OPENMSX_EXECUTABLE environment variable; otherwise it auto-detects common locations.
