mc-mod-config
Related Servers
Alternatives to mc-mod-config
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceManages, edits, backups, and validates Claude Desktop and other client JSON configurations.5-
- AlicenseNot gradedqualityCmaintenanceEnables reading, validating, and managing Minecraft resource packs, including structure checks, asset listing, pack comparison, and Modrinth queries.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing configuration file tools for AI agents. Parse, validate, merge, convert, and diff configuration files across all common formats.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceConfig Validator AI - MCP server providing AI-powered tools and automation by MEOK AI Labs6 npm70 PyPIMIT
- 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.MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP client to detect Claude Code configuration that is silently ignored, such as agent files that fail to load, unknown frontmatter fields, parent-folder settings, conflicting MCP server entries and drift since a baseline. Exposes read-only tools that return findings with exact edits, the fix prompt, and explanations of each check, without modifying any files.Apache 2.0
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.