Minecraft Mods MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_PATHS | No | Optional delimiter-separated absolute paths to extra Minecraft server folders. Use ':' on macOS/Linux and ';' on Windows. | |
| CURSEFORGE_INSTANCES_DIR | No | Path to the CurseForge instances folder. Defaults to ~/curseforge/minecraft/Instances on macOS/Linux and %USERPROFILE%\curseforge\minecraft\Instances on Windows. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Read-only system check for a new computer: Node version, CurseForge Instances folder, readable packs, and whether diagnose logs exist. Run this first on a new device. Does not change files. |
| list_instancesA | List CurseForge Minecraft instances on this PC (name, version, loader, mod counts). |
| get_instanceA | Get a summary of one CurseForge instance. Defaults to the current instance. |
| use_instanceA | Select the current CurseForge instance for later world/mod/config tools. |
| register_serverB | Remember a dedicated Minecraft server folder for compare/diagnose. |
| list_modsB | List mods (and optional resource packs) on the current instance. |
| analyze_modsB | Analyze the current instance for missing deps, duplicate jars, missing files, and incompatibilities. |
| compare_modsB | Compare mod jars between two instances, or an instance and a registered/server mods folder. |
| list_worldsA | List world profiles and save folders on the current instance. |
| create_worldB | Create a world profile inside the current instance. Optionally pick a dep-safe subset of ~N mods. Does not generate terrain; you create/open the world in-game after apply. |
| set_world_modsC | Enable or disable specific mods on a world profile. Required dependencies of enabled mods are kept automatically. |
| apply_worldA | Apply a world profile to the instance: enable/disable jars and write config patches. Do this before launching. |
| reset_worldA | Backup then delete a world save so the next launch generates it fresh with current configs. Keeps the profile. |
| list_configsB | List config files on the current instance (and a world’s serverconfig if named). |
| read_configA | Read a config file relative to the current instance root. |
| edit_configA | Change a key in a config file. Worldgen/server configs backup+reset the world by default so the next launch uses the new values. |
| recommend_modsA | Suggest mods to add or remove for a world (or the whole instance) to hit a target count and keep dependencies. |
| list_logsA | List log and crash-report files on the current instance. |
| read_logB | Read a log or crash report (tail or search; never dumps the whole huge file). |
| diagnoseA | Parse latest.log, debug.log, and recent crash reports for missing mods, mixins, and likely culprits. |
| apply_fixA | Disable crash-culprit mods on a world profile after backup. Optionally reset the world. Always prefer this over deleting jars. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools target a distinct resource and action, and descriptions clarify their roles well. Some overlap exists between diagnose and analyze_mods, and apply_world/set_world_mods/apply_fix all modify mod state, but each has a distinct intent.
The naming is predominantly verb_noun snake_case, which is predictable and easy to scan. Minor deviations like health_check and diagnose break the pattern slightly, but they do not create real confusion.
21 tools is on the heavy side for a single server, though each tool does serve a distinct purpose in the instance/world/mod/config/log workflow. The count feels borderline rather than bloated or thin.
The server covers the main lifecycle well: selecting instances, listing/analyzing mods, managing worlds, editing configs, and diagnosing/fixing issues. Minor gaps like no delete_world, unregister_server, or direct remove_mod tool are workable around with existing disable/reset flows.