mc-changelog-mcp
Queries the Modrinth API for Minecraft mod version history and uses that version information to enrich generated modpack changelogs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mc-changelog-mcp Compare my old and new modpack folders and generate a Markdown changelog"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mc-changelog-mcp
MCP server for Minecraft modpack changelog generation and version comparison.
Tools
Tool | Description |
| Compare two modpack directories and list added/removed/changed mods |
| Generate a Markdown-format changelog from a modpack directory |
| Generate a plain-text summary (suitable for Discord/forum posts) |
| Query Modrinth for a mod's version history (requires network) |
| Save a generated changelog to a file |
| Generate a full changelog including Modrinth version info for each mod |
Related MCP server: mc-pack-builder-mcp
Quick Start
npm install
npm run build
node dist/index.jsMCP Client Configuration
{
"mcpServers": {
"mc-changelog": {
"command": "node",
"args": ["${workspaceFolder}/dist/index.js"]
}
}
}Path note:
${workspaceFolder}resolves to the project root in Trae/VS Code. On other editors use the absolute path:["C:/path/to/mc-changelog-mcp/dist/index.js"](把C:/path/to/替换成你的实际路径)。
Configuration
本工具零配置即可用(内置默认值,任何环境开箱即用)。以下项目可通过环境变量或项目根目录 .env 文件覆盖(复制 .env.example 为 .env):
变量 | 默认值 | 说明 |
|
| Modrinth API 根地址,支持自建网关/代理 |
|
| 请求 User-Agent(Modrinth 要求标明来源) |
|
| 整合包内模组所在子目录名 |
|
| 增强信息(enrich)时每个模组返回的版本数量上限 |
优先级:环境变量 > .env 文件 > 内置默认值。改动后重启 MCP server 生效。
Testing
npm run build
npm run test:unit # Unit tests (100% offline)
npm test # Integration tests (requires network for Modrinth API)Requirements
Node.js 18+
@modelcontextprotocol/sdk,zodNetwork access required only for
get_mod_version_infoandgenerate_full_changelog
Architecture
mc-changelog-mcp/
├── src/
│ ├── index.ts # MCP server + all tool implementations
│ └── changelog-templates.json # Changelog template definitions
├── dist/ # Compiled JavaScript
├── skills/
│ └── mc-changelog-helper.md # Trae Work skill
├── __tests__/
│ └── unit.test.ts # Unit tests (fully offline)
├── test.js # Integration test runner
├── test_logs/ # Test output logs (gitignored)
├── package.json
├── tsconfig.json
└── .gitignoreLicense
MIT
Available Tools
6 toolscompare_modpacksA
比较两个整合包目录的差异,返回新增、删除、更新的模组列表
Inputs: new_pack_dir (required), old_pack_dir (required).
generate_changelogC
根据整合包差异生成 Markdown 格式的 Changelog
Inputs: new_pack_dir (required), old_pack_dir (required), new_version, old_version.
generate_full_changelogA
生成包含 Modrinth 版本历史信息的完整 Changelog(网络请求较多,较慢)
Inputs: new_pack_dir (required), old_pack_dir (required), format, new_version, +1 more.
generate_text_summaryB
生成简洁的纯文本格式变更记录,适合复制粘贴到 Discord/论坛/群聊
Inputs: new_pack_dir (required), old_pack_dir (required), new_version, old_version.
get_mod_version_infoB
查询 Modrinth 上某个模组的历史版本信息(发布日期、加载器支持等)
Inputs: mod_name (required), limit.
save_changelogB
将生成的 Changelog 保存到指定文件路径
Inputs: content (required), output_path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
Compare two JSON files deeply, regardless of order. Get a detailed difference report highlighting…
Create, update, and publish changelog entries on your Patchlog changelog from any MCP client.
Changelogs for apps, games and operating systems. Ask what shipped since the version you run.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceGenerate professional changelogs from git history and suggest semver bumps, with optional AI enhancement via Claude.42 npm2MIT
- AlicenseAqualityBmaintenanceEnables creating Minecraft modpack structures, searching Modrinth mods, resolving dependencies, and checking compatibility.857 npmMIT
- AlicenseAqualityCmaintenanceEnables reading, validating, comparing, and cleaning up Minecraft mod configuration files in .cfg, .toml, and .json formats.661 npmMIT
- AlicenseBqualityCmaintenanceEnables reading, validating, and managing Minecraft resource packs, including structure checks, asset listing, pack comparison, and Modrinth queries.945 npmMIT