Skip to main content

dos-mcp

Small MCP tools for a loopback-only DOSBox-X QMP server. Ghidra's maintained GDB TraceRMI agent owns debugger state; this server supplies emulator control, paced keyboard input, bounded memory reads, screenshots, and snapshots.

Tools

  • dosbox_status, dosbox_pause, dosbox_resume, and dosbox_reset
  • dosbox_swap_floppy
  • dosbox_send_keys, dosbox_key_event, and dosbox_type_text
  • dosbox_break_on_next_exec
  • dosbox_read_memory and dosbox_capture_screen
  • dosbox_save_state and dosbox_load_state

Inline memory responses are capped at 4 KiB and returned as hex. Reads up to 64 KiB can instead be written to an absolute output_path. Typed text is paced and capped at 128 US-ASCII characters; it is convenient shell input, not a cycle-deterministic keyboard primitive. Use dosbox_key_event to hold and release keys. The guest must actively consume its BIOS keyboard ring while text is sent; a busy program can silently lose input. State paths must be absolute ASCII paths, and saves do not replace an existing file unless overwrite=true.

Input, reset, state, and capture operations require running execution. QMP memory reads default to requiring a paused emulator because a running read can be torn; allow_running=true opts into that explicitly. QMP pause can be resumed through dosbox_resume; a GDB stop must be continued through GDB. DOSBox-X zero-fills unreadable physical addresses, so an unmapped byte cannot be distinguished from a real zero through this QMP interface. dosbox_swap_floppy advances the pre-mounted image list for A: or B: without injecting a host-side keyboard shortcut.

Each tool call opens one local QMP session, completes the QMP handshake, performs its commands serially, and disconnects. Requests are never retried: a timed-out mutation may already have happened, so inspect emulator state before repeating it.

This server requires the DOSBox-X remote-debug fork, built with --enable-remotedebug and configured with [dosbox] qmpserver=true. DOSBox-X accepts one QMP client at a time; do not attach another monitor while using this MCP server.

Configuration

The server uses 127.0.0.1 and never accepts a remote QMP host.

  • DOSBOX_X_QMP_PORT defaults to 4444.
  • DOSBOX_X_QMP_TIMEOUT defaults to 35 seconds.

Run with:

uv run dos-mcp

Apache-2.0.

Metadata

Release files for dos-mcp 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dos-mcp 0.1.2
File Size Uploaded Provenance
dos_mcp-0.1.2.tar.gz 100.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for dos-mcp 0.1.2
File Interpreter ABI Platform
dos_mcp-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 115.6 kB

Release files / dos_mcp-0.1.2.tar.gz

Download URL dos_mcp-0.1.2.tar.gz
Size 100.2 kB
Tags Source
SHA-256 checksum
How to use checksums
c300ca256f2642bcb7eb381151f8941dad2d5a4b56947e4b6bd563163cad332f
BLAKE2b-256 checksum
How to use checksums
d7b9b189852b981125228cc4ad6deee28ce7e3c383c706168e0f5b4da43a7381
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / dos_mcp-0.1.2-py3-none-any.whl

Download URL dos_mcp-0.1.2-py3-none-any.whl
Size 15.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a2b0cb756acb3d557753d7b9a45c1d260aaa42d72db5eba83e4fb31c5d6d4089
BLAKE2b-256 checksum
How to use checksums
7f832055226d002ef5a1f2cfbb1c80e258fc4dbdf95b4974ae7275576f087063
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for dos-mcp 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page