romm-mcp
Related Servers
Alternatives to romm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenance10 tool MCP server for RomM. Adds searching, metadata, tracking, saves and management via MCP.285MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for searching, verifying, and managing game ROM collections. Enables Internet Archive ROM search, checksum verification, save file parsing, and ROM downloads.31 npmMIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Nexus Mods mod discovery and research, backed by the v2 GraphQL API, enabling search of games, mods, collections, and users.106 npm1ISC
- FlicenseBqualityBmaintenanceA safety-first local MCP server for ROM reverse-engineering, enabling project status checks, file verification, Bakugan DS build/quality tasks, and read-only DeSmuME/ARM9 debugging.52-
- AlicenseAqualityAmaintenanceA version-aware MCP server that provides the World of Warcraft retail AddOn API with pinned documentation snapshots, enabling lookups, searches, comparisons, and diffs of APIs across patches.12457 npmApache 2.0
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides tools to query the official MCP Registry.452 npm3MIT
TDQS
Scored across 26 tools
Each tool targets a distinct resource/action pair: normal collections and smart collections are clearly separated, ROM metadata updates are distinct from user-property updates, and list/get operations are consistently paired. No two tools appear to do the same thing, and the collection membership tools are clearly differentiated from collection deletion.
The vast majority of tools follow a consistent snake_case verb_noun pattern such as list_roms, create_rom_note, and update_smart_collection. The main deviation is 'health', which is a noun rather than a verb_noun name, and the add/remove membership tools use a slightly different prepositional pattern, though they are internally consistent with each other.
26 tools is just above the heavy range, but the count is defensible because the surface spans platforms, ROMs, notes, normal collections, smart collections, users, and play sessions. Still, the separate normal/smart collection CRUD groups and the split between ROM metadata and user properties make the tool set feel borderline over-scoped.
Normal collections, smart collections, and notes have full lifecycle coverage, while ROMs support listing, fetching, metadata updates, and user-property updates. The main gap is intentional: there is no ROM file create/delete/upload functionality, and play sessions are list-only, but these exclusions are consistent with the safety bounds described in the tool definitions.