dosbox-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dosbox-mcplist files in the current DOS directory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
dosbox-mcp
MCP server for dosbox-automation: drive a DOS machine from an AI agent.
dosbox-automation is a DOSBox fork with a built-in automation API. This bridge connects any MCP-capable agent runtime (Claude Code and friends) to a running emulator. The agent can type into DOS programs, read the screen, capture frames and video, run sandboxed Lua scripts, and inspect memory: everything the automation API offers, as MCP tools.
Quick start
Install dosbox-automation and start it with the API enabled. The manual covers setup for all platforms.
Add the bridge to your MCP client. For Claude Code:
claude mcp add dosbox -- uvx dosbox-mcpOr in a JSON MCP configuration:
{ "mcpServers": { "dosbox": { "command": "uvx", "args": ["dosbox-mcp"] } } }pipx install dosbox-mcporpip install dosbox-mcpwork just as well; the command isdosbox-mcpeither way.
That's it. The bridge finds the running emulator, checks what it can
do, and registers the matching tools. Ask your agent for bridge_status
to confirm the connection.
Related MCP server: windows98-mcp
Configuration
Optional. Write a commented config file to tune the port, spawn an emulator on demand, or limit what an agent may do:
dosbox-mcp setup --initThe comments in the generated file explain each setting. Environment
variables DOSBOX_API_URL and DOSBOX_API_TOKEN override it. The
bridge talks to loopback addresses only; it will not reach out to a
remote machine.
What the agent gets
Tools for session control, screen text and captures, video recording, Lua scripting, keyboard and mouse input, and memory access. You choose how much reach an agent has, from read-only observation to full control.
An open protocol
The contract between this bridge and the emulator is written down in PROTOCOL.md and versioned independently. dosbox-automation is the reference implementation; any DOSBox variant that speaks the protocol works with this bridge.
In the box
Like the games it drives, this one ships with its paper. The feelies/
folder holds the manual, a reference card for every tool, an install
sheet, and a tech-support page.
Requirements
Python 3.11 or newer
A running dosbox-automation (0.84-da2 or newer) on the same machine
License
GPL-2.0-or-later. See LICENSE. The protocol specification (PROTOCOL.md) is licensed CC-BY-SA-4.0.
This project is developed with tooled assistance, but tested, reviewed and signed off by a human developer.
This server cannot be deployed
Maintenance
Related MCP Connectors
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI to observe and control the DOS game Master of Orion 2 by reading emulator memory and simulating mouse/keyboard input.2MIT
- AlicenseBqualityAmaintenanceControls a real Windows 98 VM through 47 MCP tools, enabling screenshots, mouse/keyboard input, command execution, and file transfers.8580 npm2MIT
- FlicenseAqualityBmaintenanceEnables an MCP client to observe and control a text-mode DOS system via a Python bridge, supporting keyboard input and screen capture.8-
- FlicenseNot gradedqualityBmaintenanceThis MCP server enables AI agents to inspect and control the native DOSBox-X debugger through bounded MCP tools, including breakpoint management, execution control, register/memory inspection, and disassembly for DOS program debugging and reverse engineering.1-