changelog-mcp
Related Servers
Alternatives to changelog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Patchlog that lets AI agents write, update, and publish changelog entries directly to your public Patchlog changelog. Supports listing projects and entries, creating drafts, publishing, and scheduling entries.622 npmMIT
- AlicenseNot gradedqualityFmaintenanceA local MCP server that records completed tasks to daily JSONL files and promotes substantial work to a cumulative weekly Markdown worklog, providing persistent, searchable logs of AI-assisted productivity.MIT
- AlicenseAqualityAmaintenanceRepository-native protocol and MCP server for coordinating work items, documentation, changelogs, and project memory between humans and AI agents, using Markdown files in a Git repository as the canonical data source.303MIT

md-log-mcpofficial
AlicenseAqualityBmaintenanceAn MCP server that lets AI coding agents save immutable, versioned Markdown reports into md-log, a human-in-the-loop review and archive layer for vibe coding.1558 npm3MIT- AlicenseNot gradedqualityDmaintenanceA local-first MCP server for AI programming branch notes and mainline decision logging, supporting branch management, summary merging, and Markdown export with optional Git-mode for isolated branch conversations.3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing persistent, local-first memory for AI agents via Markdown files in a git repo, with search, branching, and auditability.5 npm2MIT
TDQS
Scored across 15 tools
Each tool targets a distinct action: store verification, initialization, config, versioning, entry CRUD, release lifecycle, rendering, search, migration. No two tools overlap in purpose; even preview_release vs create_release clearly differ in write vs dry-run.
All tool names follow a consistent snake_case verb_noun pattern (verify_store, init_changelog, get_current_version, add_entry, etc.). The pattern is uniform across read, write, and lifecycle operations.
Fifteen tools is at the upper bound but each serves a distinct need in changelog management (entries, releases, config, rendering, import). The set remains well-scoped without redundant utilities.
The domain covers entry CRUD, release creation/preview, config init and read, version calculation, rendering, verification, and migration. Minor gaps exist (no release update/delete, no direct get_entry), but releases appear intentionally immutable and entries are accessible via list/search.