OxyROMon vs ROM Manager

oxyROMon is a free, cross-platform command-line tool for organizing and archiving ROM collections. Written in Rust, it checks files against known-good databases and supports console, computer and arcade systems through Logiqx DAT files. Commands can import, validate, check, convert, export and purge ROMs, as well as create M3U playlists for multi-disc games. It is designed for original and lossless formats; exporting to lossy formats leaves the lossless files untouched. Collections can be sorted by region or in 1G1R mode, while arcade sets can be grouped by BIOS, parent and clone. Settings are stored in SQLite with global options and per-system overrides. The documented database sources include No-Intro and Redump for consoles, and MAME or FBNeo for arcade systems. An optional server provides a GraphQL endpoint and web interface for browsing collections, managing settings, and importing ROMs and DATs. The server defaults to loopback, but URL imports can reach hosts accessible to it, so exposing the server beyond loopback requires care. No-Intro DAT handling checks for updates but does not download the DAT files.

ROM Manager is free, MIT-licensed software for organizing and converting retro console game ROMs. Its pipeline extracts archives, renames files using known game codes, converts ISO or WBFS images to CHD or RVZ, and cleans up files. It can create missing cue sheets for BIN tracks. Interfaces include a command-line tool, Python API facade, MCP server, and optional agent server with an AG-UI web interface. CLI and MCP tools can manage a self-hosted RomM library through its REST API using Basic or OAuth2 authentication. MCP tools cover conversion, game-code lookup and naming, and RomM resource groups, with environment toggles controlling domains. The server supports stdio, Streamable HTTP, and SSE transports; authentication is configurable, with none as the local default. Local conversion needs no service URL or credentials, while RomM access requires server details and credentials or a token. Conversion depends on external chdman and dolphin-tool binaries; extraction uses 7z or optional backends. Destructive cleanup can remove source files, so backups are advised.