fizlog-mcp
OfficialRelated Servers
Alternatives to fizlog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to create conventional Git commits, update changelogs, and optionally push changes to remote repositories.22MIT
- AlicenseNot gradedqualityAmaintenanceProvides a local, queryable mirror of changelogs from Anthropic and related AI dev tools, enabling agents to discover cross-product workflows and sync updates via MCP.10 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to query real-time SaaS pricing tiers, compare developer tools side-by-side, and retrieve recent product changelogs.4MIT
- AlicenseAqualityDmaintenanceEnables safe changelog management for AI assistants with append-only entries, automatic versioning, and backups to prevent accidental deletion or formatting inconsistencies.89 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to read git commits from local repositories and generate beautifully formatted, categorized changelogs.23 npmMIT
- AlicenseAqualityCmaintenanceEnables AI to manage RSS subscriptions, fetch and summarize news, and organize results into tools like Notion.912 npm3MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: read public changelog entries vs. publish a new entry. An agent can easily tell which to use for a given request, with no overlap.
Both names use snake_case with a leading verb (get_, publish_), which is consistent. However, get_public_changelog inserts an adjective and refers to 'changelog' while publish_entry refers to 'entry', a minor noun mismatch.
Two tools for a changelog service is borderline thin. While the core read/publish workflow is covered, basic management operations like updating or deleting entries would require more tools.
The surface lacks update, delete, and list-own-drafts operations, which are standard for a changelog domain. An agent asked to edit a published entry or manage drafts would hit a dead end.