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.

Install See it run

Monkey Island's lookout answering as written, then with a line written into memory
  1. The game's own line
  2. The line SCRY wrote
  1. YouMake the lookout say "Nothing, if you're a Scry debugger."
  2. Clientwrite(ref="82DD:000C", data_hex="1c6e…6c61")
  3. SCRY{"bytes_written": 128, "verified": true}

Install

Three steps. Choose your emulator here and your client in step 2: every block changes to match.

Your emulator
  1. Get the server

    You need git, uv and a MAME built with its gdbstub and its console plugin, on macOS or Windows.

    Shell
    $ git clone https://github.com/scry-mcp/scry-mame$ cd scry-mame

    You 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-x
  2. Add it to your client

    Your client

    Run this from the clone. --scope user makes the server available to you across all projects, and claude mcp list shows it.

    Shell
    $ claude mcp add --scope user mame -- uv run --directory "$PWD" scry-mame

    Run this from the clone. --scope user makes the server available to you across all projects, and claude mcp list shows it.

    Shell
    $ claude mcp add --scope user dosbox-x -- uv run --directory "$PWD" scry-dosbox-x

    Run this from the clone. codex mcp list shows the server.

    Shell
    $ codex mcp add mame -- uv run --directory "$PWD" scry-mame

    Run this from the clone. codex mcp list shows the server.

    Shell
    $ codex mcp add dosbox-x -- uv run --directory "$PWD" scry-dosbox-x

    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": {
        "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.json to have the server everywhere, or in .cursor/mcp.json inside 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.json to have the server everywhere, or in .cursor/mcp.json inside 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.json in 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.json in 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 list shows the server.

    Shell
    $ copilot mcp add mame -- uv run --directory "$PWD" scry-mame

    Run this from the clone. copilot mcp list shows the server.

    Shell
    $ copilot mcp add dosbox-x -- uv run --directory "$PWD" scry-dosbox-x

    Run this from the clone. --scope user keeps it in your own settings, and gemini mcp list shows it, disabled while the folder you are in is not trusted.

    Shell
    $ gemini mcp add --scope user mame uv run -- --directory "$PWD" scry-mame

    Run this from the clone. --scope user keeps it in your own settings, and gemini mcp list shows 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-x

    Put this in ~/.gemini/config/mcp_config.json for every workspace, or in .agents/mcp_config.json inside 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.json for every workspace, or in .agents/mcp_config.json inside 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 user keeps it in your own configuration, ~/.config/devin/mcp_config.json, and devin mcp list shows the server.

    Shell
    $ devin mcp add --scope user mame -- uv run --directory "$PWD" scry-mame

    Run this from the clone. --scope user keeps it in your own configuration, ~/.config/devin/mcp_config.json, and devin mcp list shows the server.

    Shell
    $ devin mcp add --scope user dosbox-x -- uv run --directory "$PWD" scry-dosbox-x

    Any 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-mame

    Any 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-x
  3. Ask your first question

    It needs only a ROM mamedev.org gives away, starfire.zip, in ~/roms:

    Ask

    Start starfire from ~/roms, checked against its first program ROM unzipped from starfire.zip, and show me the screen.

    Your client calls start, which answers rom_check: OK with the game stopped at its first instruction, and screen_view, which returns the picture.

    It needs only Bricks, a small game this repository builds:

    Ask

    Start DOSBox-X on demos/bricks/bricks.conf from its folder, stopping at the program's own int 3. Run to it and tell me where DOS loaded the program.

    Your client calls start and resume, which stops at the program's own int 3 and 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.

  • MAMEWhat is in this register, this byte, this routine, right now?

    registers, read_memory, disassemble

    With your symbol file loaded you say Player1, not 0x008400.

  • MAMEWho writes this byte?

    watch_add

    A watch stops the game on the instruction that changes the byte, and the reply names it.

  • MAMEWhere does the game keep its credits?

    scan

    It narrows a range of memory to the bytes that changed the way the value did.

  • DOSBox-XWhat is in this variable, this register, right now?

    read_memory, registers, disassemble

    With your symbol table loaded you say _engine_set_rate, not 00AF:0017A6EC.

  • DOSBox-XWhat did the program log?

    log, log_wait

    A program that writes to port 0xE9 has a log the server can search and wait on.

  • DOSBox-XWho changes this variable?

    watch_add, breakpoint_at

    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.

And Deluxe Paint by its menus, ReChip!, X-COM Apocalypse.

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.