Skip to main content
Glama
mc-pack-builder-mcp

mc-pack-builder-mcp

Related Servers

Alternatives to mc-pack-builder-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search, read, and publish Minecraft mods on Modrinth, including creating projects and uploading jar files as new versions.
      7
      310 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      6
      55 npm
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Minecraft modpack development by generating FTB Quests chapters and tasks, KubeJS scripts (weapons, armor, recipes), validating SNBT/config files, and providing diagnostic checks.
      22 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Search Thunderstore mods, resolve dependencies, check mod packs for outdated or broken mods, and export r2modman profiles. Not affiliated with or endorsed by Thunderstore.
      5
      49 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues