changelog
Related Servers
Alternatives to changelog
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceChange tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.8188 PyPI26MIT

fizlog-mcpofficial
AlicenseAqualityCmaintenanceEnables AI assistants like Claude and Cursor to publish, schedule, or save changelog entries as drafts, delivering them to an in-app widget, public changelog page, and RSS feed with optional subscriber email. It can also read recent published entries so assistants can summarize releases or avoid duplicates.238 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to prove that previously working behavior still works after code changes by running the product through the same steps twice and surfacing only unintended differences as actionable findings.26 npmMIT
- AlicenseAqualityCmaintenanceTurns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.11MIT
- AlicenseAqualityDmaintenancePrivacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.2851 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables managing daily change logs with automatic formatting, intelligent monitoring, and client-ready output, helping developers document work and generate professional reports.MIT
TDQS
Scored across 2 tools
log_change records a new change while check_changes evaluates already-logged changes. They operate on different phases of the same lifecycle, so there is no practical ambiguity about which tool to call.
Both tool names follow a clear verb_noun pattern: log_change and check_changes. The naming style is consistent and immediately communicates each tool's action.
Two tools is below the typical 3-15 range, but the server is narrowly scoped to logging and evaluating changes. Each tool is necessary and the pair covers the full intended workflow without redundancy.
The server covers the complete lifecycle for its stated purpose: log a user-visible change, then check whether that change moved a metric. There are no obvious dead ends or missing operations for this narrow domain.