mc-pack-builder-mcp
Related Servers
Alternatives to mc-pack-builder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables reading, validating, and managing Minecraft resource packs, including structure checks, asset listing, pack comparison, and Modrinth queries.953 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to search, read, and publish Minecraft mods on Modrinth, including creating projects and uploading jar files as new versions.7310 npm1MIT
- AlicenseAqualityBmaintenanceEnables comparing Minecraft modpack directories to identify added, removed, and changed mods, and generating Markdown or plain-text changelogs. It can also enrich changelogs with Modrinth version history and save generated output to files.655 npmMIT
- FlicenseAqualityCmaintenanceEnables MCP clients like Cursor to manage local CurseForge Minecraft instances by creating world-specific mod profiles, editing configs, diagnosing crashes, and applying changes on disk before launching the game.21-
- AlicenseNot gradedqualityBmaintenanceEnables Minecraft modpack development by generating FTB Quests chapters and tasks, KubeJS scripts (weapons, armor, recipes), validating SNBT/config files, and providing diagnostic checks.22 npmMIT

PackWardenofficial
AlicenseAqualityBmaintenanceSearch Thunderstore mods, resolve dependencies, check mod packs for outdated or broken mods, and export r2modman profiles. Not affiliated with or endorsed by Thunderstore.549 npmMIT
TDQS
Scored across 8 tools
Most tools have clearly distinct resource+action targets (create_pack, search_mods, get_mod_info, export_standard_pack). The one soft overlap is resolve_dependencies vs generate_dependency_list, and get_pack_info's 'detect common issues' versus check_pack_compatibility, but descriptions distinguish them adequately.
All eight tools follow a consistent snake_case verb_noun pattern (create_pack, get_pack_info, search_mods, resolve_dependencies, check_pack_compatibility, generate_dependency_list, export_standard_pack). No mixing of conventions or vague standalone verbs.
Eight tools is well within the ideal 3-15 range and each maps to a distinct stage of the modpack workflow (create, inspect, search, resolve, verify, export). No obvious filler tools.
The surface covers creation, inspection, mod discovery, dependency resolution, compatibility checking, and export, but there is no tool to add or remove a mod from an existing pack, which is a core lifecycle operation. Export helps but agents cannot directly mutate pack contents, leaving a notable gap.