Project
Amiga DevBench (amiga_mcp)
A cross-development environment that connects a modern machine to an emulated or real Amiga over serial — live debugging, memory inspection, remote execution, and MCP tools so Claude Code can build and drive Amiga software.
Classic Amiga development is painful: no source-level debugger on the target, no network stack on a stock machine, and a crash takes the whole OS with it. Amiga DevBench bridges a modern host and the Amiga over a serial link so I can write C on my Mac, cross-compile it in Docker, and deploy, run, inspect, and debug it on the Amiga in one loop — and so can Claude Code, through MCP.
What it does
-
Write C on macOS, cross-compile for m68k in Docker, and deploy to the emulator in one command.
-
Live-inspect memory, registers, tasks, libraries, and volumes on the running Amiga.
-
Register variables in an Amiga program and read or write them from the host in real time; define "hooks" the host can call into the running program.
-
Launch, stop, and break programs; run AmigaDOS scripts; read and write files; manage assigns, processes, and protection bits.
-
A source-level debugger: breakpoints, step into and over, registers, and call stack.
-
A web dashboard and 45-plus MCP tools covering build, deploy, logging, memory, variables, and processes — with CRC32 deployment checks and live log tailing.
How it is built
A small daemon on the Amiga (amiga-bridge) talks to client programs over Exec message
ports and to the host over serial.device. On the host, a Python server speaks that serial
protocol (over TCP or a PTY to FS-UAE) and exposes it three ways: a web UI with an SSE event
stream, a REST API, and an MCP server for Claude Code. Programs link a small client library
(ab_init, ab_register_var, ab_poll, ab_cleanup) to take part. An optional patched
FS-UAE build adds an HTTP debugger for the emulator itself.
The example games and demos live in a companion repository, amiga_games.