ROM Manager
github.com
- Free plan
- Linux
- API
- Self-hosted
What ROM Manager is
ROM Manager is a free, MIT-licensed tool 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 also create missing cue sheets for BIN tracks. The project offers a command-line interface, a Python API facade, an MCP server, and an optional agent server with an AG-UI web interface. The 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; environment toggles control which tool domains are enabled. The MCP server supports stdio, Streamable HTTP, and SSE transports, with configurable authentication and none as the local-tool default. Local conversion needs no service URL or credentials, but RomM features require a configured server and credentials or token. Conversion requires external chdman and dolphin-tool binaries; archive extraction uses 7z or optional archive backends. Conversion and delete or clean-origin options can remove source files, so the project advises backing up ROMs first.
Who it suits
ROM Manager suits people managing retro console ROM collections who want CLI, Python API, MCP, or agent-server options. RomM library management is available for users with a configured self-hosted server.
Good to know, and what to watch
- Converts ISO and WBFS images to CHD or RVZ.
- Generates missing cue sheets for BIN tracks.
- Offers CLI, Python API, MCP, and agent interfaces.
- Can manage a self-hosted RomM library.
- Conversion requires external chdman and dolphin-tool binaries.
- Some archive extraction options require 7z or other backends.
- Conversion and cleanup options can remove source files.
Plans
Every plan and priceROM Manager
Open source
The verdict
ROM Manager combines ROM conversion and organization with several ways to work with the tools. Back up source files first, and account for the external binaries required for conversion.
What the maker publishes
- Conversion
- Its pipeline extracts archives, renames ROMs using known game codes, converts ISO/WBFS images to CHD or RVZ, and cleans up files. source
- Cue sheets
- It can generate missing cue sheets for BIN tracks. source
- Dependencies
- Conversion requires external chdman and dolphin-tool binaries, while archive extraction uses 7z or optional archive backends. source
- Dependencies
- Conversion uses external chdman and dolphin-tool binaries, and archive extraction uses 7z or optional archive backends. source
- Deployment
- The MCP server can run locally over stdio or use streamable HTTP transport, and the project documents container deployment. source
- Destructive operations
- Conversion and delete or clean-origin options can remove source files, and the project advises backing up ROMs first. source
- Destructive operations
- The project warns users to back up ROMs because conversion and options that delete or clean up source files can be destructive. source
- Intended use
- The project is aimed at managing retro console game ROMs and exposes installation options for CLI/API, MCP, agent, native archive support, or all features. source
- Intended users
- The project describes ROM Manager as a tool for managing retro console game ROMs and documents CLI, Python API, MCP, and agent usage. source
- Interfaces
- The project provides a CLI, Python API facade, MCP server, and optional agent server with an AG-UI web interface. source
- Interfaces
- It provides a command-line interface, an API facade, an MCP server, and an optional Pydantic-AI agent server with an AG-UI web interface. source
- License
- The project is MIT licensed by Knuckles-Team. source
- License
- The repository states that ROM Manager is MIT licensed and credits Knuckles-Team. source
- MCP tools
- MCP tools cover conversion, game-code lookup and naming, and RomM resource groups, with tool domains controlled by environment toggles. source
- MCP tools
- The MCP server exposes action-routed tools for ROM conversion and game-code lookup, with tool domains configurable through environment toggles. source
- Network security
- For RomM connections, the configuration supports TLS profiles and requires peer and hostname verification. source
- Purpose
- ROM Manager converts and organizes game ROMs, with an MCP server and optional A2A agent. source
- Purpose
- ROM Manager converts and organizes game ROMs, including extracting archives, renaming by known game codes, converting ISO/WBFS images to CHD or RVZ, and generating cue sheets. source
- RomM integration
- The CLI and MCP tools can manage a RomM self-hosted library through its REST API using Basic or OAuth2 authentication. source
- RomM integration
- The RomM REST client can manage a running RomM library, with Basic or OAuth2 authentication configured through environment variables. source
- Security
- The project describes the converter as a local tool that needs no service URL or credentials; RomM features require a configured server URL and credentials or token. source
- Security
- The project describes ROM Manager as a local tool that needs no service URL or credentials for local conversion. source
- Telemetry
- The project lists native OpenTelemetry exports and supports configuration for trace and metric export. source
- Transport
- The MCP server supports stdio, Streamable HTTP, and SSE transports; the README lists authentication as configurable, with none as the local-tool default. source
Checked against the maker's pages on 11 Oct 2026.