mc-changelog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODRINTH_API_BASE | No | Modrinth API root URL. Supports self-hosted gateways/proxies. | https://api.modrinth.com/v2 |
| CHANGELOG_MODS_DIR | No | Subdirectory name inside the modpack where mods are located. | mods |
| CHANGELOG_USER_AGENT | No | User-Agent used for requests. Modrinth requires identifying the source. | mc-changelog-mcp/1.0 |
| CHANGELOG_ENRICH_LIMIT | No | Maximum number of versions returned per mod when enriching information. | 5 |
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 |
|---|---|
| compare_modpacksA | 比较两个整合包目录的差异，返回新增、删除、更新的模组列表 |
| generate_changelogC | 根据整合包差异生成 Markdown 格式的 Changelog |
| generate_text_summaryB | 生成简洁的纯文本格式变更记录，适合复制粘贴到 Discord/论坛/群聊 |
| get_mod_version_infoB | 查询 Modrinth 上某个模组的历史版本信息（发布日期、加载器支持等） |
| save_changelogB | 将生成的 Changelog 保存到指定文件路径 |
| generate_full_changelogA | 生成包含 Modrinth 版本历史信息的完整 Changelog（网络请求较多，较慢） |
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
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.