AI导哈

Amiga开发工作台

Amiga DevBench 是一个从现代计算机开发 Amiga 软件的一体化开发工作台，提供 Web 仪表盘和 MCP 工具，用于构建程序、传输文件、运行 AmigaDOS 命令以及检查模拟或真实 Amiga 设备。

  • by geekychris
  • Python
  • 本地部署
  • 51 星标
  • 更新于
在 GitHub 查看 geekychris/amiga_mcp

使用说明

Amiga DevBench

Develop Amiga software from a modern computer. DevBench provides a web dashboard and MCP tools for building programs, transferring files, running AmigaDOS commands and inspecting an emulated or real Amiga.

New here? Install and verify DevBench. The guide works from an existing checkout and starts with a simulator, so you can verify the host installation before setting up an Amiga.

What you need

  • Host server: Python 3.10+ and Git, on macOS, Linux or Windows.
  • A real target: an emulator with your own ROM/OS, or an Amiga, running the amiga-bridge guest program. The simulator needs neither.
  • Compiling Amiga programs: Docker and the appropriate cross-compiler image. Docker is not needed just to install the Python server or inspect a target with an existing bridge.

Setup in three commands

scripts/setup.sh     # install everything that can be installed (68k, os4 or both)
scripts/doctor.sh    # check every prerequisite; each problem comes with its fix
scripts/start.sh     # start the emulators + devbenches, wait until the Amigas answer

To pick a machine from a full-screen menu instead (classic Amiga, AmigaOS 4, Atari ST and 3DO), run make retro. It runs the Retro Launcher from ../retro-launcher.

The Kickstart ROM and the AmigaOS 3.x / 4.1 installs are commercial, so doctor.sh keeps reporting them until they're in place; it says where each goes. The scripts are bash: on Windows, use WSL (or scripts/install.ps1). See SETUP.md for the one-page guide.

The current server is in amiga-devbench/ (Python). The mcp-server/ TypeScript project and amiga-debug-lib/ are deprecated.

Start here

I want to… Read
Set up and start everything with the scripts SETUP.md
Install from a checkout and verify it works Installation guide
Connect Codex CLI or Claude Code MCP client setup
Use WinUAE or FS-UAE Dual-emulator setup
Connect an emulator or physical Amiga Target setup
Set up AmigaOS 4.1 on QEMU AmigaOS 4 setup
Use WinUAE native debugging WinUAE debugger
Choose between guest and emulator debugging Debugger guide
Find a tool or API Documentation index

How it fits together

Codex / Claude Code ── MCP over HTTP ──┐
                                     ├── DevBench ── serial/TCP ── amiga-bridge
Web browser ───────── HTTP ───────────┘                              (Amiga)

The dashboard is at http://localhost:3000/; the MCP endpoint is http://localhost:3000/mcp. scripts/start.sh runs one DevBench per target: AmigaOS 4 on port 3000 and classic 68k on port 3001. DevBench must stay running while clients use it.

Most guest tools work through the bridge. Native WinUAE debugging uses WinUAE's built-in GDB server. Emulator-level amiga_fsuae_* tools separately require patched FS-UAE. Installing the Python server does not install an emulator, ROM or AmigaOS.

Browse the examples · Architecture · Scripted installer · MIT license

相关 MCP