Tool Groups

Tool Groups Reference

Exact contents of each group, pulled directly from server.py's TOOL_GROUPS dict. Enable via MODHELPER_MCP_ENABLED_TOOLS (see Getting Started).

modrinth (10 tools)

modrinth_search, modrinth_get_project, modrinth_get_project_versions, modrinth_get_best_version, modrinth_get_version, modrinth_get_download_url, modrinth_download_file, modrinth_check_for_update, modrinth_get_dependencies, modrinth_download_with_dependencies.

No API key required for any of these; MODRINTH_API_KEY only raises rate limits.

curseforge (9 tools)

curseforge_list_games, curseforge_search_mods, curseforge_get_mod, curseforge_get_mod_files, curseforge_get_best_file, curseforge_get_download_url, curseforge_download_file, curseforge_get_mod_dependencies, curseforge_download_with_dependencies.

CURSEFORGE_API_KEY is required for every tool in this group.

nexus (7 tools)

validate_api_key, find_games, search_mods, get_mod, list_mod_files, get_download_links, download_mod_file.

These are Nexus Mods tools, not Minecraft-specific - Nexus hosts mods for many games. NEXUS_API_KEY required.

thunderstore (5 tools)

thunderstore_list_communities, thunderstore_search_packages, thunderstore_get_package, thunderstore_get_package_version, thunderstore_download_package.

Thunderstore is mainly used for other games (Lethal Company, Valheim, etc), not Minecraft - only relevant if you mod outside Minecraft too.

steam (4 tools)

steam_search_workshop, steam_get_workshop_details, steam_get_workshop_download_info, steam_download_workshop_file.

For Steam Workshop content, not applicable to Minecraft mods specifically. STEAM_API_KEY required.

git (2 tools)

clone_source_reference, download_mdk_template.

This is the group that covers the "identify and clone a mod's GitHub repo" workflow, plus fetching official Mod Development Kit templates (NeoForge/Forge/Fabric) to bootstrap a new project. See Examples.

docs (3 tools)

search_reference_code, sync_platform_documentation, search_platform_documentation.

Full-text search over local reference code/docs, and syncing platform documentation for offline/fast lookup. Distinct from the knowledge group below - this one searches whatever docs/code you've already synced or cloned locally; knowledge is a separate, pre-built modding-concepts database.

dev (4 tools)

setup_dev_server, launch_dev_client, configure_mod_template, cleanup_workspace_references.

Bootstraps a dev server/client and can refactor a freshly cloned template package (renaming package paths, mod id, etc), plus a cache-cleanup tool.

knowledge (15 tools)

explain_concept, get_example, search_modding_docs, get_minecraft_version_info, search_mappings, get_class_details, lookup_obfuscated, get_method_signature, list_mapping_versions, browse_package, search_mod_examples, get_mod_example, list_canonical_mods, list_mod_categories, get_mod_patterns.

This is a SQLite-backed knowledge base (requires the mcmodding-mcp indexer to have been run first) covering Parchment mappings (class/method/ field/obfuscated-name lookup) and canonical mod examples (Create, Botania, AE2) with pattern search. Useful for "how does mod X typically implement Y" questions without needing that mod's source cloned locally.

automation (25 tools)

bot_connect, bot_disconnect, bot_move_control, bot_look_at, bot_get_position, bot_move_to, bot_send_chat, bot_check_inventory, bot_equip_item, bot_inventory_details, bot_toss_item, bot_get_nearby_entities, bot_attack_entity, bot_use_on_entity, bot_follow_entity, bot_dig_block, bot_place_block, bot_open_container, bot_withdraw_item, bot_deposit_item, bot_close_container, bot_get_recipes, bot_craft_item, bot_get_nearby_players, bot_get_server_info.

Requires Node.js and the MineFlayer npm package to actually connect a bot to a running server. This group is dead weight if you don't have a bot connection running - only enable it when you're actively testing in-game behavior through a bot, not for general modding work.