PackWarden
OfficialRelated Servers
Alternatives to PackWarden
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables creating Minecraft modpack structures, searching Modrinth mods, resolving dependencies, and checking compatibility.8391 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to search, browse, and manage mods across Nexus Mods, mod.io, Thunderstore, and Modrinth, as well as perform local diagnostics like detecting games and parsing crash logs.MIT
- AlicenseBqualityBmaintenanceEnables reading, validating, and managing Minecraft resource packs, including structure checks, asset listing, pack comparison, and Modrinth queries.9417 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.121 npm1ISC
- AlicenseAqualityBmaintenanceEnables publishing and updating mod releases, editing mod descriptions, metadata and tags, and reading or replying to comments and notifications on the Vintage Story ModDB from any MCP client. Includes a one-time manual login helper that stores a reusable session cookie for authenticated write operations.1513 npmMIT
- AlicenseBqualityBmaintenanceEnables interacting with Nexus Mods: search and download mods, manage endorsements and uploads, and use a browser session for comments, forums, and private messages.2257Creative Commons Attribution Non Commercial 4.0 International
TDQS
Scored across 5 tools
Each tool targets a distinct action: listing communities, searching mods, resolving dependencies, auditing a pack, and exporting a profile. There is mild overlap between resolve_dependencies and check_pack_health (both report missing dependencies) and between resolve_dependencies and export_r2modman_profile (which can optionally resolve), but the descriptions clearly delineate the primary intent of each.
All five tools follow a strict verb_noun snake_case pattern: resolve_dependencies, search_mods, check_pack_health, export_r2modman_profile, list_communities. No camelCase or stylistic deviations; 'r2modman' is a proper noun used consistently within a well-formed name.
Five tools is a tight, purpose-fit surface for a Thunderstore/r2modman pack workflow: discover, search, resolve, validate, export. No tool feels redundant or vestigial, and nothing obviously needed for the core loop is missing from the count.
The surface covers discovery through export, but has notable gaps: no way to inspect a single mod's details/version history, no tool to read or parse an existing profile (import is only via the external manager), and no explicit dependency download/fetch step. Agents can work around some of this via resolve_dependencies and search_mods, but profile inspection is a dead end.