mc-mod-config
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOD_CONFIG_EXTENSIONS | No | 支持扫描/解析的配置文件扩展名（逗号分隔，可扩展自定义扩展名） | cfg,toml,json |
| MOD_CONFIG_MAX_FILE_MB | No | 单个配置文件大小上限（MB），超过则跳过 | 50 |
| MOD_CONFIG_MAX_STRING_LEN | No | 校验时字符串值长度告警阈值 | 500 |
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 |
|---|---|
| read_mod_configA | Read and parse a mod config file (.cfg for Forge, .toml for Fabric, .json for any). Returns the parsed config tree. |
| list_mod_configsA | List all mod config files in a config directory (recursively). Returns file path, mod ID, format, and size. |
| validate_mod_configsB | Validate all mod config files in a directory for common issues: empty values, invalid numbers, parse errors, oversized strings. |
| compare_mod_configsA | Compare two config directories (e.g. before/after a modpack update). Reports added, removed, changed, and unchanged config files with key-level diff info. |
| find_orphaned_configsA | Find config files whose mod JAR is no longer present in the mods/ directory. Useful after removing mods. |
| get_mod_default_configA | Get the known default/baseline config for a specific mod. Supports Sodium, OptiFine, Phosphor, Lithium, Fabric API. |
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 6 tools
Each tool targets a distinct operation: reading, listing, validating, comparing, finding orphaned configs, and retrieving defaults. There is no meaningful overlap, and even read_mod_config vs get_mod_default_config are clearly separated by actual vs baseline config.
All tool names follow a consistent verb_noun snake_case pattern. Singular and plural forms are used appropriately for the object, so the naming is predictable and uniform.
Six tools is a well-scoped size for a config inspection and audit server. Each tool covers a meaningful workflow without redundancy or bloat.
The toolset covers the full apparent read/audit lifecycle: discovering, reading, validating, comparing, finding orphaned configs, and getting baseline defaults. It intentionally does not include writing/editing, but that does not create a gap for the server's evident diagnostic purpose.