Romm MCP Server

MCP server for RomM — self-hosted game and ROM management platform

Remote serverstreamable-httpGo

What is the Romm MCP MCP server?

Romm MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Romm MCP directly instead of describing what you should do. MCP server for RomM — self-hosted game and ROM management platform.

What you get

Give your AI assistant full access to browse, search, and manage your retro game library.

  • Browse — your full ROM library with pagination, filtering, and sorting
  • Search — games by name across all platforms
  • Platforms — — list all platforms with ROM counts and metadata
  • Collections — — create, list, update, and delete game collections
  • ROM details — — full metadata including genres, companies, ratings, summaries
  • Firmware — — list available firmware files per platform

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Romm MCP is connected, these are the calls the assistant has available:

  • romm_stats — Library statistics — total platforms, ROMs, saves, states, screenshots, file size
  • romm_list_platforms — List all platforms with ROM counts, categories, and slugs
  • romm_browse_roms — Browse and filter ROMs with pagination. Supports platform, collection, genre, company, region filters, and sorting
  • romm_get_rom — Full ROM details by ID — metadata, genres, companies, summary, rating, YouTube link
  • romm_search_roms — Search ROMs by name
  • romm_manage_collections — CRUD collections (list, get, create, update, delete). Also supports smart and virtual collections
  • romm_get_collection_roms — List all ROMs in a specific collection
  • romm_list_firmware — List firmware files available per platform
  • romm_download_rom — Generate an authenticated download URL for a ROM
  • romm_update_rom — Update ROM metadata — display name, notes, favorite status
  • romm_rom_notes — Manage notes attached to a ROM (list, add, update, delete)
  • romm_manage_saves — List save files, optionally filtered by ROM

Configuration and credentials

You will need 2 environment variables: ROMM_BASE_URL, ROMM_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js >= 20.0.0 - A running RomM instance (v5.0+) - A RomM API key (rmm_* token)

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Romm MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the romm mcp mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Romm MCP's toolset — romm_stats, romm_list_platforms, romm_browse_roms and 11 more — is a fair guide to whether it matches your workflow. It is maintained by rodrigosiviero; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
romm_statsLibrary statistics — total platforms, ROMs, saves, states, screenshots, file size
romm_list_platformsList all platforms with ROM counts, categories, and slugs
romm_browse_romsBrowse and filter ROMs with pagination. Supports platform, collection, genre, company, region filters, and sorting
romm_get_romFull ROM details by ID — metadata, genres, companies, summary, rating, YouTube link
romm_search_romsSearch ROMs by name
romm_manage_collectionsCRUD collections (list, get, create, update, delete). Also supports smart and virtual collections
romm_get_collection_romsList all ROMs in a specific collection
romm_list_firmwareList firmware files available per platform
romm_download_romGenerate an authenticated download URL for a ROM
romm_update_romUpdate ROM metadata — display name, notes, favorite status
romm_rom_notesManage notes attached to a ROM (list, add, update, delete)
romm_manage_savesList save files, optionally filtered by ROM
romm_manage_statesList save state files, optionally filtered by ROM
romm_systemSystem operations — heartbeat, config, trigger library scan, metadata update

How to install the Romm MCP MCP server

{
  "mcpServers": {
    "romm": {
      "command": "npx",
      "args": ["-y", "romm-mcp"],
      "env": {
        "ROMM_BASE_URL": "http://your-romm-instance:5500",
        "ROMM_API_KEY": "rmm_your_api_key_here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js >= 20.0.0 - A running RomM instance (v5.0+) - A RomM API key (rmm_* token)
VariableDescriptionRequired
ROMM_BASE_URLEndpoint or connection string the server talks to.Yes
ROMM_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Romm MCP to romm stats.
  • Use Romm MCP to romm list platforms.
  • Use Romm MCP to romm browse roms.

Frequently asked questions

It connects Romm MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (romm_stats, romm_list_platforms, romm_browse_roms, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Romm MCP directly.