=== See the CHANGELOG.md ===
An MCP server that runs a Color Computer 3 in MAME. An AI assistant can type BASIC, mount disks, take screenshots, and read or write memory.
This copy is set up for Windows 10 or newer. Linux and macOS need the same pieces, with paths adjusted.
- Node.js 20 or newer
- MAME and your own CoCo 3 ROMs (
coco3.zip) - ToolShed
decb, only if you usecoco_build_disk
MAME, ROMs, and ToolShed are not included. Install those yourself.
ROMs and other CoCo software: Color Computer Archive.
Put mame.exe and a roms folder in mame/, or point .env at a MAME install you already have. See mame/README.md.
For disk builds, put decb.exe in toolshed/. See toolshed/README.md.
From the MCP folder:
copy .env.example .envEdit .env so MAME_PATH, MAME_ROMPATH, and DECB_PATH match your machine.
The canonical defaults are MAME_MACHINE=coco3h (HD6309), COCO_RAM=2M, and
COCO_MONITOR=rgb. These can be overridden in .env; monitor choices are rgb
and composite. The monitor setting is a CoCo input configuration, not a host
display option. Before launch, the MCP regenerates its own
MCP/work/mame-cfg/<machine>.cfg with the monitor selection and passes that
directory to MAME with -cfg_directory. Changes made in MAME's UI to that generated
machine config are reset at the next MCP launch.
Save states are discovered at MCP/states/<configured-machine>/<name>.sta.
The launch explicitly sets -statename %g to keep MAME and the lookup aligned.
npm install
npm run buildThe same npm install, npm run build, npm start, and npm test commands work from the repo root. They just run the MCP copies.
Point your MCP client at MCP/dist/index.js. Use the coco_start tool to launch MAME. Don't start MAME yourself first.
MCP/storage/disks/ disk images (.dsk)
MCP/storage/host/bas/ BASIC source on the PC
MCP/storage/host/bin/ .BIN files
MCP/storage/host/data/ other files
Mount with a path like storage/disks/game.dsk. That path is resolved from the MCP folder. See MCP/storage/README.md.
Agentic AI was used in partial creation of this app.
The default MPI layout is slot 1 empty, slot 2 Speech/Sound Pak (ssc),
slot 3 empty, and slot 4 Disto Super Controller II (scii) with its Disto
RTC (rtime). Glenside IDE is not required. MAME_SLOTS can override the map;
MAME_SLOTS={"ext":"fdc"} retains a plain FDC configuration.
Use EOU swapboot option 3 (EMUHWARECLOCK) for automatic RTC time.
The clock must remain accessible in slot 4 with this guest Clock2 module.
Option 4 instead prompts for date/time; it was rejected for the canonical setup.
Preserve the trailing montype r command when swapboot replaces startup.
MAME_BOOT_FLOPPY=../media/63EMU.DSK and
MAME_VHD=../media/63SDC-MCP-DEV.VHD select the EOU media. The VHD uses MAME's
independent hard1/vhd0 device, without an IDE cartridge. Never mount the
immutable stock 63SDC.VHD. Speech/Sound needs pic-7040-510.bin and
sp0256-al2.bin; SCII uses Disto C-DOS 3 v1.2 ROM, not the standard FDC ROM.
This is an intentional tradeoff to retain the verified automatic RTC path.



