mc-changelog-mcp
Related Servers
Alternatives to mc-changelog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables creating Minecraft modpack structures, searching Modrinth mods, resolving dependencies, and checking compatibility.8MIT
- AlicenseBqualityBmaintenanceEnables reading, validating, and managing Minecraft resource packs, including structure checks, asset listing, pack comparison, and Modrinth queries.90MIT
- AlicenseAqualityBmaintenanceEnables reading, validating, comparing, and cleaning up Minecraft mod configuration files in .cfg, .toml, and .json formats.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables developers and AI agents to compute deterministic in-memory unified diffs between successive versions of live artifacts and receive structured change telemetry in return. It runs with zero external dependencies and plugs into MCP-compliant clients such as Claude Desktop, Cursor, and Windsurf.8-
- AlicenseNot gradedqualityDmaintenanceGenerate professional changelogs from git history and suggest semver bumps, with optional AI enhancement via Claude.20 npm2MIT
- AlicenseAqualityCmaintenanceEnables generating conventional-commit–grouped release notes and CHANGELOG.md drafts from a local repository's git log between tags or commits, plus grouping commits by type. Reads only local git history via an MCP client such as Cursor or Claude Desktop.3MIT
TDQS
Scored across 6 tools
The three generation tools have overlapping-sounding names, but their descriptions clarify distinct outputs: full changelog with Modrinth history, diff-based Markdown changelog, and plain-text summary. get_mod_version_info and generate_full_changelog overlap somewhat on Modrinth data, but one is a lookup and the other an aggregation, so boundaries are mostly clear.
All tool names use consistent snake_case with a clear verb-first pattern (generate_*, compare_*, get_*, save_*). Minor pluralization in compare_modpacks is harmless and still predictable.
Six tools is well-scoped for a changelog-generation server, covering comparison, generation variants, metadata lookup, and saving. Each tool has a clear purpose and none feels redundant.
The surface covers the core lifecycle: compare modpacks, generate Markdown or text summaries, enrich with Modrinth history, and save output. Minor gaps exist around customizing or appending to existing changelogs, but agents can work around them.