MCP servers for MAME and DOSBox-X
See inside the machine
SCRY holds an emulator open so your AI client can debug the program inside: stop it, read memory by name, press its inputs.

- The game's own line
- The line SCRY wrote
- YouMake the lookout say "Nothing, if you're a Scry debugger."
- Client
write(ref="82DD:000C", data_hex="1c6e…6c61") - SCRY
{"bytes_written": 128, "verified": true}
Install
Three steps. Choose your emulator here and your client in step 2: every block changes to match.
Get the server
You need git, uv and a MAME built with its gdbstub and its
consoleplugin, on macOS or Windows.Shell$ git clone https://github.com/scry-mcp/scry-mame$ cd scry-mameYou need git, uv and a DOSBox-X built with its debugger, on macOS or Windows.
Shell$ git clone https://github.com/scry-mcp/scry-dosbox-x$ cd scry-dosbox-xAdd it to your client
Run this from the clone.
--scope usermakes the server available to you across all projects, andclaude mcp listshows it.Shell$ claude mcp add --scope user mame -- uv run --directory "$PWD" scry-mameRun this from the clone.
--scope usermakes the server available to you across all projects, andclaude mcp listshows it.Shell$ claude mcp add --scope user dosbox-x -- uv run --directory "$PWD" scry-dosbox-xRun this from the clone.
codex mcp listshows the server.Shell$ codex mcp add mame -- uv run --directory "$PWD" scry-mameRun this from the clone.
codex mcp listshows the server.Shell$ codex mcp add dosbox-x -- uv run --directory "$PWD" scry-dosbox-xIn Settings, open the Developer tab and choose Edit Config, which opens
claude_desktop_config.json; add this with the clone's absolute path. Then quit Claude Desktop completely and start it again.JSON{ "mcpServers": { "mame": { "command": "uv", "args": ["run", "--directory", "/path/to/scry-mame", "scry-mame"] } } }In Settings, open the Developer tab and choose Edit Config, which opens
claude_desktop_config.json; add this with the clone's absolute path. Then quit Claude Desktop completely and start it again.JSON{ "mcpServers": { "dosbox-x": { "command": "uv", "args": ["run", "--directory", "/path/to/scry-dosbox-x", "scry-dosbox-x"] } } }Put this in
~/.cursor/mcp.jsonto have the server everywhere, or in.cursor/mcp.jsoninside one project, with the clone's absolute path.JSON{ "mcpServers": { "mame": { "type": "stdio", "command": "uv", "args": ["run", "--directory", "/path/to/scry-mame", "scry-mame"] } } }Put this in
~/.cursor/mcp.jsonto have the server everywhere, or in.cursor/mcp.jsoninside one project, with the clone's absolute path.JSON{ "mcpServers": { "dosbox-x": { "type": "stdio", "command": "uv", "args": ["run", "--directory", "/path/to/scry-dosbox-x", "scry-dosbox-x"] } } }Put this in
.vscode/mcp.jsonin your workspace, with the clone's absolute path.JSON{ "servers": { "mame": { "type": "stdio", "command": "uv", "args": ["run", "--directory", "/path/to/scry-mame", "scry-mame"] } } }Put this in
.vscode/mcp.jsonin your workspace, with the clone's absolute path.JSON{ "servers": { "dosbox-x": { "type": "stdio", "command": "uv", "args": ["run", "--directory", "/path/to/scry-dosbox-x", "scry-dosbox-x"] } } }Run this from the clone.
copilot mcp listshows the server.Shell$ copilot mcp add mame -- uv run --directory "$PWD" scry-mameRun this from the clone.
copilot mcp listshows the server.Shell$ copilot mcp add dosbox-x -- uv run --directory "$PWD" scry-dosbox-xRun this from the clone.
--scope userkeeps it in your own settings, andgemini mcp listshows it, disabled while the folder you are in is not trusted.Shell$ gemini mcp add --scope user mame uv run -- --directory "$PWD" scry-mameRun this from the clone.
--scope userkeeps it in your own settings, andgemini mcp listshows it, disabled while the folder you are in is not trusted.Shell$ gemini mcp add --scope user dosbox-x uv run -- --directory "$PWD" scry-dosbox-xPut this in
~/.gemini/config/mcp_config.jsonfor every workspace, or in.agents/mcp_config.jsoninside one, with the clone's absolute path.JSON{ "mcpServers": { "mame": { "command": "uv", "args": ["run", "--directory", "/path/to/scry-mame", "scry-mame"] } } }Put this in
~/.gemini/config/mcp_config.jsonfor every workspace, or in.agents/mcp_config.jsoninside one, with the clone's absolute path.JSON{ "mcpServers": { "dosbox-x": { "command": "uv", "args": ["run", "--directory", "/path/to/scry-dosbox-x", "scry-dosbox-x"] } } }Run this from the clone.
--scope userkeeps it in your own configuration,~/.config/devin/mcp_config.json, anddevin mcp listshows the server.Shell$ devin mcp add --scope user mame -- uv run --directory "$PWD" scry-mameRun this from the clone.
--scope userkeeps it in your own configuration,~/.config/devin/mcp_config.json, anddevin mcp listshows the server.Shell$ devin mcp add --scope user dosbox-x -- uv run --directory "$PWD" scry-dosbox-xAny client that runs a local server over stdio starts this command, with the clone's absolute path.
Shell$ uv run --directory /path/to/scry-mame scry-mameAny client that runs a local server over stdio starts this command, with the clone's absolute path.
Shell$ uv run --directory /path/to/scry-dosbox-x scry-dosbox-xAsk your first question
It needs only a ROM mamedev.org gives away,
starfire.zip, in~/roms:AskStart
starfirefrom~/roms, checked against its first program ROM unzipped fromstarfire.zip, and show me the screen.Your client calls
start, which answersrom_check: OKwith the game stopped at its first instruction, andscreen_view, which returns the picture.It needs only Bricks, a small game this repository builds:
AskStart DOSBox-X on
demos/bricks/bricks.conffrom its folder, stopping at the program's ownint 3. Run to it and tell me where DOS loaded the program.Your client calls
startandresume, which stops at the program's ownint 3and gives its address, whose segment is where DOS loaded it.
What you can ask
Plain questions. Your client turns each one into the tools under it.
- MAME
What is in this register, this byte, this routine, right now?
registers, read_memory, disassemble
With your symbol file loaded you say
Player1, not0x008400. - MAME
Who writes this byte?
A watch stops the game on the instruction that changes the byte, and the reply names it.
- MAME
Where does the game keep its credits?
It narrows a range of memory to the bytes that changed the way the value did.
- DOSBox-X
What is in this variable, this register, right now?
read_memory, registers, disassemble
With your symbol table loaded you say
_engine_set_rate, not00AF:0017A6EC. - DOSBox-X
What did the program log?
A program that writes to port
0xE9has a log the server can search and wait on. - DOSBox-X
Who changes this variable?
Stop when it changes, count every value it takes, or record every write without stopping.
Every tool, with an example you can try: the reference.
See it run
Each demo is a script its repository runs against the real emulator. The pictures move because they are that run.
Monkey IslandThe Secret of Monkey Island, with the lookout's lines written into the game's memory while it is stopped; it needs the disc.DOSBox-X
LineUpThe arcade LineUp, from the game's own ROM set, played by its own routine and variable names.MAME · DOSBox-X
Star FireExidy's Star Fire, a free ROM, from a cold start to the instruction that counts its coins.MAME
GridleeVidea's Gridlee, a free ROM, whose credits turn out to live in two bytes, in binary and in BCD.MAME
Speed FightThe arcade Speed Fight, from a copy of the game, started from a file in its.scry/folder.MAME · DOSBox-X
BricksA breakout game this repository builds, stopped by name where each brick falls.DOSBox-X
MinesweeperA Minesweeper this repository builds, its mines read out of memory and the board cleared without a miss.DOSBox-X
Deluxe PaintDeluxe Paint II paints a sunset, and a scan finds the byte that holds its colour; it needs the program.DOSBox-X
Two emulators, one way of asking
A tool both servers have means the same and answers the same. What differs is what the emulators themselves make different.
MAME
Ask your AI client what an arcade game is doing, and it finds out: it stops the game, reads its memory and presses its controls.
DOSBox-X
Ask your AI client what a DOS program is doing, and it finds out: it stops the program, reads its memory and presses its keys.