Skip to main content
Glama
dtz-labs

zesarux-mcp

by dtz-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to zesarux-mcp

No user-submitted related servers found.

    Related Servers

    • dos-mcp

      64kramsystem
      A
      license
      B
      quality
      B
      maintenance
      MCP server providing emulator control for a loopback-only DOSBox-X QMP server, with tools for keyboard input, memory reads, screenshots, and state snapshots to complement Ghidra's GDB TraceRMI debugging.
      13
      1
      Apache 2.0

    • 80mcp

      avwohl
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run CP/M, MP/M, and DOS packages on Z80/x86 emulators, inspect byte-exact results and files, and debug the emulators themselves over the Model Context Protocol.
      7
      GPL 3.0

    • mcp-pine

      dmang-dev
      A
      license
      A
      quality
      C
      maintenance
      MCP server for PCSX2 and other emulators that speak the PINE protocol. Read and write 8/16/32/64-bit emulator memory and control save states for PlayStation-family emulation.
      14
      18 npm
      2
      MIT

    • mcp-retroarch

      dmang-dev
      A
      license
      A
      quality
      C
      maintenance
      MCP server for RetroArch via its Network Control Interface. Drive any libretro core — read/write memory, save/load state, screenshot, pause/frame-advance/reset — across NES, SNES, Genesis, N64, GBA, PS1 and more.
      17
      13 npm
      3
      MIT

    • beebjit-mcp

      acscpt
      A
      license
      A
      quality
      B
      maintenance
      Lets an AI application instantiate, connect to, drive, capture output from, and interrogate a real BBC Micro emulator.
      22
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., assemble vs. disassemble, peek vs. hexdump). The only potential overlap is between get_screen and save_screen, which both save screen files but with different emphasis. Overall, an agent can reliably distinguish tools.

    Naming Consistency4/5

    The vast majority of tool names follow a verb_noun pattern with underscores (e.g., clear_breakpoint, set_register, send_keys). A few names like snapshot_inram and tape_control deviate from this pattern, making the set slightly inconsistent.

    Tool Count2/5

    With 34 tools, the count significantly exceeds the recommended range of 3–15. While the tools cover many emulator features, the number is high and could overwhelm an agent, leading to selection difficulties.

    Completeness4/5

    The tool set covers most major emulator operations: launch, memory, CPU, breakpoints, screen, snapshots, tape, AY player, and more. Minor gaps exist, such as missing tape transport commands and no direct OCR tool, but core workflows are well-supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources