ToolBB-0025

MCP-AmigaOS4: drive real AmigaOne machines and QEMU guests from an agent

MCP-AmigaOS4 drives AmigaOS 4.1 machines through 138 MCP tools and a daemon on each Amiga, on QEMU guests and real PowerPC hardware alike. Tools edit files, run AmigaDOS commands, take screenshots and install the OS. On an AmigaOne X5000 it reads sensors through the board's MCU and switches power over an FTDI cable. The README says both targets were verified.

Open original source github.com · derfsss

Claimed
Why this evidence label?

README says it was verified end to end on QEMU Pegasos2 and a real AmigaOne X5000; no logs or photos checked.

How we check entries
Preview image for MCP-AmigaOS4: drive real AmigaOne machines and QEMU guests from an agent
The source's own preview image, from github.com.

Briefing

The system has two halves. amiga-fleet-mcp, a Python server on the workstation, manages one or more Amigas and talks to QEMU for start, stop, snapshots and a GDB stub. MCPd, a small C daemon on each Amiga, serves JSON-RPC over TCP port 4322 and answers discovery on UDP port 4323. SandboxVM wraps test programs and drivers, so a crash in a guest program does not take the daemon down.

The power tools need an FTDI USB-to-TTL cable wired to the X5000's P18 or the A1222's P15 header; the README calls this the only software path to boot a fully-off X5000. The keyboard and mouse input tools are off by default and can only be enabled by an action on the Amiga itself. The project is BSD-3-Clause.

From the GitHub API

Repository facts

Repository facts for derfsss/mcp-amigaos4, from the GitHub API
Repositoryderfsss/mcp-amigaos4
Stars7
LicenseBSD-3-Clause Permissive
LanguagePython
Last push3 Oct 2026 26 d ago

Tags

Report a problem with this entry