dos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOSBOX_X_QMP_PORT | No | The QMP port used by the DOSBox-X server. | 4444 |
| DOSBOX_X_QMP_TIMEOUT | No | The QMP timeout in seconds. Defaults to 35 seconds. | 35 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dosbox_statusC | Report DOSBox-X run and debugger state. |
| dosbox_pauseA | Pause DOSBox-X execution. |
| dosbox_resumeB | Resume DOSBox-X execution. |
| dosbox_resetA | Reset the DOS guest, optionally without a full machine reset. |
| dosbox_swap_floppyA | Advance the mounted floppy image in A: (0) or B: (1). |
| dosbox_break_on_next_execB | Break GDB at the next DOS EXEC entry point. |
| dosbox_send_keysC | Tap one simultaneous chord of DOSBox-X QKeyCode names. |
| dosbox_key_eventC | Press or release one DOSBox-X QKeyCode key. |
| dosbox_type_textC | Type paced US-ASCII text while the guest actively consumes input. |
| dosbox_read_memoryC | Read physical memory; unmapped bytes are indistinguishable from zero. |
| dosbox_capture_screenA | Capture the current DOSBox-X display as an MCP PNG image. |
| dosbox_save_stateB | Save emulator state to an absolute host path. |
| dosbox_load_stateB | Load emulator state from an existing absolute host path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct emulator function, but the input-related tools (send_keys, key_event, type_text) are somewhat similar in purpose. The descriptions clarify the differences, but an agent might occasionally confuse send_keys with key_event.
All tools consistently use the dosbox_ prefix and snake_case. Most use an imperative verb (capture, save, load, pause, resume, reset, swap, break, send, type, read), but a few are nouns (status, key_event), which is a minor deviation.
With 13 tools, the server covers the key aspects of DOSBox control—state, input, display, memory, and execution—without being bloated. The count feels well-scoped for an emulator control surface.
The tool set covers core emulator operations such as state save/load, screen capture, keyboard input, and memory reads. Minor gaps exist, such as mouse control or disk image management, but the surface is largely sufficient for typical DOSBox automation.